Apply suggestions from code review

Co-authored-by: Todd Baert <[email protected]>
Signed-off-by: James Milligan <[email protected]>

Author: james-milligan

README.md

@@ -15,7 +15,7 @@
 
 ## Get started
 
-The OpenFeature Operator is a Kubernetes native operator that allows you to expose feature flags to your applications. It injects a [flagD](https://github.com/open-feature/flagd) sidecar into your pod and allows you to poll the flagD server for feature flags in a variety of ways. To get started, follow the installation instructions in the [docs](./docs).
+The OpenFeature Operator allows you to expose feature flags to your applications. It injects a [flagD](https://github.com/open-feature/flagd) sidecar into relevant pods exposes gRPC and HTTP interfaces for flag evaluation. To get started, follow the installation instructions in the [docs](./docs).
 
 ## Contributing
 

docs/feature_flag_configuration.md

@@ -27,6 +27,6 @@ spec:
 
 Within the CRD there are 2 main objects, namely the `flagDSpec` and the `featureFlagSpec`, both offering a different set of configuration for the injected `flagd` sidecars.
 
-The `featureFlagSpec` is a json object representing the flag configurations themselves, the documentation for this object can be found [here](https://github.com/open-feature/flagd/blob/main/docs/configuration/flag_configuration.md).
+The `featureFlagSpec` is an object representing the flag configurations themselves, the documentation for this object can be found [here](https://github.com/open-feature/flagd/blob/main/docs/configuration/flag_configuration.md).
 
 The `flagDSpec` has one property called `envs` which contains a list of environment variables used to override the default start command values in `flagd`, the documentation for this configuration can be found [here](https://github.com/open-feature/flagd/blob/main/docs/configuration/configuration.md).

docs/getting_started.md

@@ -4,7 +4,7 @@ Once you have [installed the operator](./installation.md) you can follow this gu
 
 ### Deploy a `FeatureFlagConfiguration`
 
-This `FeatureFlagConfiguration` will be watched by the injected `flagd` container and used to construct its internal flag definitions state. If multiple configurations are supplied to `flagd` these states will be merged.
+This `FeatureFlagConfiguration` is watched by the injected `flagd` container and used to construct its internal flag definitions state. If multiple configurations are supplied to `flagd` these states will be merged.
 
 ```yaml
 apiVersion: core.openfeature.dev/v1alpha2
@@ -25,7 +25,7 @@ spec:
 
 ### Reference the deployed FeatureFlagConfiguration within a Deployment spec annotation.
 
-In this example, we will be creating a `Deployment` containing an `busybox-curl` container. In the example below, the `metadata.annotations` object contains the required annotations for the operator to correctly configure and inject the `flagd` sidecar into each deployed `Pod`. The documentation for these annotations can be found [here](./annotations.md).
+In this example, a`Deployment` containing a `busybox-curl` container is created. In the example below, the `metadata.annotations` object contains the required annotations for the operator to correctly configure and inject the `flagd` sidecar into each deployed `Pod`. The documentation for these annotations can be found [here](./annotations.md).
 
 ```yaml
 apiVersion: apps/v1
@@ -66,7 +66,7 @@ Should give a similar output to the following
 NAME                                                READY   STATUS              RESTARTS   AGE
 busybox-curl-7bd5767999-spf7v                              0/2     ContainerCreating   0          2s
 ```
-If we describe our `Pod` we should should see that the injected sidecar has the following configuration:
+When the `Pod` is described, the injected sidecar has the following configuration:
 ```
 kubectl describe pod busybox-curl-7bd5767999-spf7v
 ```