adapt misses in docs

Signed-off-by: odubajDT <[email protected]>

docs/reference/flagd-cli/flagd_start.md

@@ -26,7 +26,7 @@ flagd start [flags]
   -s, --sources string                      JSON representation of an array of SourceConfig objects. This object contains 2 required fields, uri (string) and provider (string). Documentation for this object: https://github.com/open-feature/flagd/blob/main/docs/configuration/configuration.md#sync-provider-customisation
   -y, --sync-provider string                DEPRECATED: Set a sync provider e.g. filepath or remote
   -a, --sync-provider-args stringToString   DEPRECATED: Sync provider arguments as key values separated by = (default [])
-  -f, --uri .yaml/.yml/.json                Set a sync provider uri to read data from, this can be a filepath,url (http and grpc) or FeatureFlag. When flag keys are duplicated across multiple providers the merge priority follows the index of the flag arguments, as such flags from the uri at index 0 take the lowest precedence, with duplicated keys being overwritten by those from the uri at index 1. Please note that if you are using filepath, flagd only supports files with .yaml/.yml/.json extension.
+  -f, --uri .yaml/.yml/.json                Set a sync provider uri to read data from, this can be a filepath, URL (HTTP and gRPC) or FeatureFlag custom resource. When flag keys are duplicated across multiple providers the merge priority follows the index of the flag arguments, as such flags from the uri at index 0 take the lowest precedence, with duplicated keys being overwritten by those from the uri at index 1. Please note that if you are using filepath, flagd only supports files with .yaml/.yml/.json extension.
 ```
 
 ### Options inherited from parent commands

docs/reference/openfeature-operator/crds/featureflag.md

@@ -3,7 +3,7 @@
 The `FeatureFlag` version `v1beta1` CRD defines a CR with the following example structure:
 
 ```yaml
-apiVersion: core.openfeature.dev/v1alpha2
+apiVersion: core.openfeature.dev/v1beta1
 kind: FeatureFlag
 metadata:
   name: featureflag-sample

docs/reference/openfeature-operator/crds/featureflagsource.md

@@ -87,10 +87,10 @@ If no namespace is provided, it is assumed that the CR is within the same namesp
 
 In this example, 2 CRs are being used to configure the injected container (by default the operator uses the `flagd:main` image), `config-A` (which is assumed to be in the namespace `test-ns`) and `config-B` from the `test-ns-2` namespace, with `config-B` taking precedence in the configuration merge.
 
-The `FeatureFlagSource` version `v1alpha3` CRD defines a CR with the following example structure, the documentation for this CRD can be found [here](https://github.com/open-feature/open-feature-operator/blob/main/docs/crds.md#featureflagsource):
+The `FeatureFlagSource` version `v1beta1` CRD defines a CR with the following example structure, the documentation for this CRD can be found [here](https://github.com/open-feature/open-feature-operator/blob/main/docs/crds.md#featureflagsource):
 
 ```yaml
-apiVersion: core.openfeature.dev/v1alpha3
+apiVersion: core.openfeature.dev/v1beta1
 kind: FeatureFlagSource
 metadata:
     name: flag-source-sample
@@ -137,7 +137,7 @@ An example of this behavior:
 Config-A:
 
 ```yaml
-apiVersion: core.openfeature.dev/v1alpha2
+apiVersion: core.openfeature.dev/v1beta1
 kind: FeatureFlagSource
 metadata:
     name: config-A
@@ -149,7 +149,7 @@ spec:
 Config-B:
 
 ```yaml
-apiVersion: core.openfeature.dev/v1alpha2
+apiVersion: core.openfeature.dev/v1beta1
 kind: FeatureFlagSource
 metadata:
     name: config-B

flagd/cmd/start.go

@@ -54,7 +54,7 @@ func init() {
 		"a", nil, "DEPRECATED: Sync provider arguments as key values separated by =")
 	flags.StringSliceP(
 		uriFlagName, "f", []string{}, "Set a sync provider uri to read data from, this can be a filepath,"+
-			"url (http and grpc) or FeatureFlag. When flag keys are duplicated across multiple providers the "+
+			" URL (HTTP and gRPC) or FeatureFlag custom resource. When flag keys are duplicated across multiple providers the "+
 			"merge priority follows the index of the flag arguments, as such flags from the uri at index 0 take the "+
 			"lowest precedence, with duplicated keys being overwritten by those from the uri at index 1. "+
 			"Please note that if you are using filepath, flagd only supports files with `.yaml/.yml/.json` extension.",