Apply suggestions from code review

Co-authored-by: Todd Baert <todd.baert@dynatrace.com>
Signed-off-by: odubajDT <93584209+odubajDT@users.noreply.github.com>

Author: odubajDT

docs/annotations.md

@@ -33,7 +33,7 @@ Example:
 
 ### `openfeature.dev/featureflaginprocessconfiguration`
 
-This annotation specifies the names of the `FeatureFlagInProcessConfigurations` used to configure the injected environment variables.
+This annotation specifies the names of the `FeatureFlagInProcessConfigurations` used to configure the injected environment variables to support flagd's [in-process evaluation mode](https://flagd.dev/architecture/#in-process-evaluation).
 The annotation value is a comma separated list of values following one of 2 patterns: {NAME} or {NAMESPACE}/{NAME}. 
 
 If no namespace is provided, it is assumed that the custom resource is within the **same namespace** as the annotated pod.

docs/feature_flag_in_process_configuration.md

@@ -25,14 +25,12 @@ spec:
       value: "val2"
 ```
 
-## How it works?
+## How does it work?
 
 Similar to usage of [FeatureFlagSource](./feature_flag_source.md) configuration,
 [annotations](./annotations.md#) are used to allow the injection of configuration data
 into the annotated Pod.
-The mutating webhook parses the annotations, retrieves the referenced `FeatureFlagInProcessConfiguration`
-resources from the cluster and injects the data from the resource into all containers of the Pod via environment variables,
-which are read by the application using the in-process feature flag evaluation.
+The mutating webhook parses the annotations, retrieves the referenced `FeatureFlagInProcessConfiguration` resources from the cluster and injects the data from the resource into all containers of the Pod via environment variables, which configure the provider in the workload to consume feature flag configuration from the available [sync implementation](https://flagd.dev/concepts/syncs/#grpc-sync) specified by the configuration.
 
 ## Merging of configurations