docs: adjust naming conventions and style

Author: guiwrite

docs/docs/flagsmith-integration/CLI.md

@@ -33,7 +33,7 @@ FLAGS
   -o, --output=<value>    [default: ./flagsmith.json] The file path output
 
 DESCRIPTION
-  Retrieve flagsmith features from the Flagsmith API and output them to a file.
+  Retrieve flagsmith feature flags from the Flagsmith API and output them to a file.
 
 EXAMPLES
   $ FLAGSMITH_ENVIRONMENT=x flagsmith get

docs/docs/flagsmith-integration/client-side-sdks/android.md

@@ -81,7 +81,7 @@ flagsmith.getFeatureFlags { result ->
 }
 ```
 
-### Get Flags for an identity
+### Get Flags for an Identity
 
 To get feature flags for a specific identity:
 

docs/docs/flagsmith-integration/client-side-sdks/flutter.md

@@ -1,7 +1,7 @@
 ---
 title: Flagsmith Flutter SDK
 sidebar_label: Flutter
-description: Manage your Feature Flags and Remote Config in your Flutter applications.
+description: Manage your Feature Flags and Remote Config in your Flutter Applications.
 slug: /clients/flutter
 ---
 
@@ -146,7 +146,7 @@ bool isFeatureEnabled = flagsmithClient.hasCachedFeatureFlag('feature');
 
 ### Identifying users
 
-To check if a feature exists for an Identity:
+To check if a feature exists for an identity:
 
 ```dart
 final user = Identity(identifier: 'flagsmith_sample_user');
@@ -158,7 +158,7 @@ if (featureEnabled) {
 }
 ```
 
-To get the feature flag configuration value for an Identity:
+To get the feature flag configuration value for an identity:
 
 ```dart
 final myRemoteConfig = await flagsmithClient.getFeatureFlagValue('my_test_feature', user: user);
@@ -169,7 +169,7 @@ if (myRemoteConfig != null) {
 }
 ```
 
-To get the user traits for an Identity:
+To get the user traits for an identity:
 
 ```dart
 final userTraits = await flagsmithClient.getTraits(user)
@@ -180,7 +180,7 @@ if (userTraits != null && userTraits) {
 }
 ```
 
-To get the trait value for an Identity and specific Trait key:
+To get the trait value for an identity and specific trait key:
 
 ```dart
 final userTrait = await flagsmithClient.getTrait(user, 'cookies_key');
@@ -191,7 +191,7 @@ if (userTrait != null) {
 }
 ```
 
-Or get user traits for an Identity and specific Trait keys:
+Or get user traits for an identity and specific trait keys:
 
 ```dart
 final userTraits = await flagsmithClient.getTraits(user, keys: ['cookies_key', 'other_trait']);
@@ -202,7 +202,7 @@ if (userTraits != null) {
 }
 ```
 
-To update a user trait for an Identity:
+To update a user trait for an identity:
 
 ```dart
 final userTrait = await flagsmithClient.getTrait(user, 'cookies_key');

docs/docs/flagsmith-integration/client-side-sdks/javascript.md

@@ -1,15 +1,13 @@
 ---
 title: Flagsmith JavaScript SDK
 sidebar_label: JavaScript
-description: Manage your Feature Flags and Remote Config in your JavaScript applications.
+description: Manage your Feature Flags and Remote Config in your JavaScript Applications.
 slug: /clients/javascript
 ---
 
-This library can be used with pure JavaScript, React (and all other popular frameworks/libraries) and React Native
-projects. The source code for the client is available on [GitHub](https://github.com/flagsmith/flagsmith-js-client).
+This library can be used with pure JavaScript, React (and all other popular frameworks/libraries) and React Native projects. The source code for the client is available on [GitHub](https://github.com/flagsmith/flagsmith-js-client).
 
-Example applications for a variety of JavaScript frameworks such as React, Vue and Angular, as well as React Native, can
-be found here:
+Example applications for a variety of JavaScript frameworks such as React, Vue and Angular, as well as React Native, can be found here:
 
 - [Flagsmith Framework Examples](https://github.com/Flagsmith/flagsmith-js-examples/tree/main)
 
@@ -126,7 +124,7 @@ cli commands can be found [here](https://github.com/Flagsmith/flagsmith-cli).
 ## Identifying users
 
 Identifying users allows you to target specific users from the Flagsmith dashboard and configure features and traits.
-You can call this before or after you initialise the project, calling it after will re-fetch features from the API.
+You can call this before or after you initialise the project, calling it after will re-fetch feature flags from the API.
 
 You can identify the users as part of initialising the client or after with the function `flagsmith.identify`.
 
@@ -148,7 +146,7 @@ flagsmith.init({
 
   const { isFromServer } = params; //determines if the update came from the server or local cached storage
 
-  //Set a trait against the Identity
+  //Set a trait against the identity
   flagsmith.setTrait('favourite_colour', 'blue'); //This save the trait against the user, it can be queried with flagsmith.getTrait
 
   //Check for a feature
@@ -196,7 +194,7 @@ flagsmith.init({
 
   const { isFromServer } = params; //determines if the update came from the server or local cached storage
 
-  //Set a trait against the Identity
+  //Set a trait against the identity
   flagsmith.setTrait('favourite_colour', 'blue'); //This save the trait against the user, it can be queried with flagsmith.getTrait
 
   //Check for a feature
@@ -229,7 +227,7 @@ All function and property types can be seen
 
 | Property                                                                                    |                                                                                                                    Description                                                                                                                    | Required |                                         Default Value |
 | ------------------------------------------------------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | -------: | ----------------------------------------------------: |
-| `environmentID: string`                                                                     |                                                                          Defines which project environment you wish to get flags for. _example ACME Project - Staging._                                                                           |  **YES** |                                                  null |
+| `environmentID: string`                                                                     |                                                                          Defines which project environment you wish to get flags for. _example ACME project - Staging._                                                                           |  **YES** |                                                  null |
 | `onChange?: (previousFlags:IFlags, params:IRetrieveInfo, loadingState:LoadingState)=> void` |                                           Your callback function for when the flags are retrieved `(previousFlags,{isFromServer:true/false,flagsChanged: true/false, traitsChanged:true/false})=>{...}`                                           |  **YES** |                                                  null |
 | `onError?: (res:{message:string}) => void`                                                  |                                                                                         Callback function on failure to retrieve flags. `(error)=>{...}`                                                                                          |          |                                                  null |
 | `realtime?:boolean`                                                                         |                                                                                   Whether to listen for [Real Time Flag events](/advanced-use/real-time-flags)                                                                                    |          |                                                 false |

docs/docs/flagsmith-integration/flagsmith-api-overview/admin-api/code-examples.md

@@ -3,7 +3,7 @@ title: Code Examples
 sidebar_label: Code Examples
 ---
 
-Here is a simple example of how to use the Admin API with `curl` to create a new Environment within a Project.
+Here is a simple example of how to use the Admin API with `curl` to create a new environment within a project.
 
 ```bash
 curl 'https://api.flagsmith.com/api/v1/environments/' \

docs/docs/flagsmith-integration/flagsmith-api-overview/flags-api/authentication.md

@@ -9,7 +9,7 @@ The Flags API uses a non-secret **Environment Key** for authentication. This key
 
 You can find the Environment Key for each of your environments in the Flagsmith dashboard.
 
-1.  Navigate to the Project you want to work with.
+1.  Navigate to the project you want to work with.
 2.  Go to the **Environments** tab.
 3.  You will see a list of your environments, each with its own Client-side Environment Key.
 

docs/docs/flagsmith-integration/flagsmith-api-overview/flags-api/code-examples.md

@@ -16,11 +16,11 @@ curl 'https://edge.api.flagsmith.com/api/v1/flags/' \
 
 ### Get Flags for an Identified User
 
-This command performs the entire SDK Identity workflow in a single call:
+This command performs the entire SDK identity workflow in a single call:
 
-1.  Lazily creates an Identity if it doesn't already exist.
-2.  Sets or updates Traits for that Identity.
-3.  Receives the flags for that Identity, including any segment or identity-specific overrides.
+1.  Lazily creates an identity if it doesn't already exist.
+2.  Sets or updates traits for that identity.
+3.  Receives the flags for that identity, including any segment or identity-specific overrides.
 
 ```bash
 curl --request POST 'https://edge.api.flagsmith.com/api/v1/identities/' \

docs/docs/flagsmith-integration/integration-overview.md

@@ -6,7 +6,7 @@ sidebar_position: 10
 
 Flagsmith is designed to be integrated into your applications in a variety of ways, depending on your architecture and requirements. This guide provides an overview of the different integration options available.
 
-## Deciding between Front-end and Back-end Flags
+## Deciding between Front-end and Back-end Feature Flags
 
 One of the first decisions to make when integrating Flagsmith is whether to evaluate flags on the front-end (client-side) or back-end (server-side).
 

docs/docs/flagsmith-integration/openfeature.md

@@ -6,14 +6,11 @@ sidebar_position: 50
 
 # OpenFeature
 
-[OpenFeature](https://openfeature.dev/) is an open standard for feature flag management, created to support a robust
-feature flag ecosystem using cloud native technologies. OpenFeature provides a unified API and SDK, and a
-developer-first, cloud-native implementation, with extensibility for open source and commercial offerings.
+[OpenFeature](https://openfeature.dev/) is an open standard for feature flag management, created to support a robust feature flag ecosystem using cloud native technologies. OpenFeature provides a unified API and SDK, and a developer-first, cloud-native implementation, with extensibility for open source and commercial offerings.
 
-Flagsmith is proud to contribute to this initiative, and is a governance board member of this CNCF project. Our goal,
-and that of OpenFeature, is to recommend using OpenFeature as the default SDK interface for Flagsmith projects.
+Flagsmith is proud to contribute to this initiative, and is a governance board member of this CNCF project. Our goal, and that of OpenFeature, is to recommend using OpenFeature as the default SDK interface for Flagsmith projects.
 
-OpenFeature is being actively worked on; we encourage anyone interested Feature Flags and Open Source to get involved!
+OpenFeature is being actively worked on; we encourage anyone interested in feature flags and open source to get involved!
 
 ## Flagsmith OpenFeature Providers
 

docs/docs/flagsmith-integration/server-side.mdx

@@ -576,23 +576,23 @@ secret_button_feature_value = Flagsmith.Client.get_feature_value(flags, "secret_
 
 ### When running in [Remote Evaluation mode](/clients#remote-evaluation)
 
-- When requesting Flags for an Identity, all the Traits defined in the SDK will automatically be persisted against the
-  Identity within the Flagsmith API.
-- Traits passed to the SDK will be added to all the other previously persisted Traits associated with that Identity.
-- This full set of Traits are then used to evaluate the Flag values for the Identity.
+- When requesting flags for an identity, all the traits defined in the SDK will automatically be persisted against the
+  identity within the Flagsmith API.
+- Traits passed to the SDK will be added to all the other previously persisted traits associated with that identity.
+- This full set of traits are then used to evaluate the flag values for the identity.
 - This all happens in a single request/response.
 
 ### When running in [Local Evaluation mode](/clients#local-evaluation)
 
-- _Only_ the Traits provided to the SDK at runtime will be used. Local Evaluation mode, by design, does not make any
-  network requests to the Flagsmith API when evaluating Flags for an Identity.
+- _Only_ the traits provided to the SDK at runtime will be used. Local Evaluation mode, by design, does not make any
+  network requests to the Flagsmith API when evaluating flags for an identity.
     - When running in Local Evaluation Mode, the SDK requests the
       [Environment Document](/clients#the-environment-document) from the Flagsmith API. This contains all the
-      information required to make Flag Evaluations, but it does _not_ contain any Trait data.
+      information required to make flag evaluations, but it does _not_ contain any trait data.
 
 ## Managing Default Flags
 
-Default Flags are configured by passing in a function that is called when a Flag cannot be found or if the network
+Default flags are configured by passing in a function that is called when a flag cannot be found or if the network
 request to the API fails when retrieving flags.
 
 <Tabs groupId="language" queryString>
@@ -1004,9 +1004,9 @@ The Server Side SDKS share the same network behaviour across the different langu
 
 ### Remote Evaluation Mode Network Behaviour
 
-- A blocking network request is made every time you make a call to get an Environment Flags. In Python, for example,
+- A blocking network request is made every time you make a call to get an environment flags. In Python, for example,
   `flagsmith.get_environment_flags()` will trigger this request.
-- A blocking network request is made every time you make a call to get an Identities Flags. In Python, for example,
+- A blocking network request is made every time you make a call to get an identities flags. In Python, for example,
   `flagsmith.get_identity_flags(identifier=identifier, traits=traits)` will trigger this request.
 
 ### Local Evaluation Mode Network Behaviour
@@ -1019,12 +1019,12 @@ To use Local Evaluation mode, you must use a Server Side key.
 
 :::
 
-- When the SDK is initialised, it will make an asynchronous network request to retrieve details about the Environment.
-- Every 60 seconds (by default), it will repeat this aysnchronous request to ensure that the Environment information it
+- When the SDK is initialised, it will make an asynchronous network request to retrieve details about the environment.
+- Every 60 seconds (by default), it will repeat this aysnchronous request to ensure that the environment information it
   has is up to date.
 
 To achieve Local Evaluation, in most languages, the SDK spawns a separate thread (or equivalent) to poll the API for
-changes to the Environment. In certain languages, you may be required to terminate this thread before cleaning up the
+changes to the environment. In certain languages, you may be required to terminate this thread before cleaning up the
 instance of the Flagsmith client. Languages in which this is necessary are provided below.
 
 <Tabs groupId="language" queryString>