Fix Vale linting issues in Ruby feature flags docs

- Remove 'just' from sentences
- Use sentence-style capitalization for 'Remote configuration'
- Replace 'via' with 'through' for Vale compliance
- Break up long sentence using passive voice for readability

Author: sameerank

content/en/feature_flags/setup/ruby.md

@@ -69,7 +69,7 @@ The targeting key is used for consistent traffic distribution (percentage rollou
 
 After creating the `OpenFeature` client, you can start reading flag values throughout your app. Flag evaluation uses locally cached data, so no network requests occur when evaluating flags.
 
-Each flag is identified by a _key_ (a unique string) and can be evaluated with a _typed method_ that returns a value of the expected type. If the flag doesn't exist or cannot be evaluated, the SDK returns the provided default value.
+Each flag is identified by a unique string _key_. Flags are evaluated using typed methods that return values matching the expected type. The SDK returns the default value if a flag doesn't exist or cannot be evaluated.
 
 ### Boolean flags
 
@@ -155,7 +155,7 @@ timeout = config['timeout'] || 30
 
 ### Flag evaluation details
 
-When you need more than just the flag value, use the `fetch_<type>_details` methods. These methods return both the evaluated value and metadata explaining the evaluation:
+When you need more than the flag value, use the `fetch_<type>_details` methods. These methods return both the evaluated value and metadata explaining the evaluation:
 
 ```ruby
 details = client.fetch_boolean_details(
@@ -196,11 +196,11 @@ end
 If feature flags always return default values:
 
 1. Verify Remote Configuration is enabled in your Datadog Agent configuration
-2. Ensure service and environment are configured (either via `DD_SERVICE`/`DD_ENV` environment variables or `config.service`/`config.env` in Ruby)
+2. Ensure service and environment are configured (either through `DD_SERVICE`/`DD_ENV` environment variables or `config.service`/`config.env` in Ruby)
 3. Check that `config.remote.enabled = true` and `config.open_feature.enabled = true` are set in your Ruby application's Datadog configuration
 4. Verify the datadog gem version includes OpenFeature support (2.23.0 or later)
 
-### Remote Configuration connection issues
+### Remote configuration connection issues
 
 Check the Datadog tracer logs for Remote Configuration status: