fix linting issues

Signed-off-by: Michael Beemer <[email protected]>

Author: beeme1mr

docs/reference/concepts/05-events.mdx

@@ -155,4 +155,4 @@ The context associated with the provider has changed, and the provider has not y
 
 ### PROVIDER_CONTEXT_CHANGED (Static-context/Client-side only)
 
-The context associated with the provider has changed, and the provider has [reconciled](/docs/reference/concepts/sdk-paradigms#static-context-paradigms-client-side-sdks) its associated state.
+The context associated with the provider has changed, and the provider has [reconciled](/docs/reference/concepts/sdk-paradigms#static-context-paradigms-client-side-sdks) its associated state.

docs/reference/concepts/07-tracking.mdx

@@ -17,16 +17,21 @@ Tracking events associated with flag evaluations serves two primary purposes:
 
 ### Performance Monitoring
 
-When changes are made to an application via feature flags, tracking helps measure their impact on performance. By associating events with flag evaluation contexts
+When changes are made to an application via feature flags, tracking helps measure their impact on performance.
+By associating events with flag evaluation contexts
 and sending this data to telemetry or analytics platforms, teams can determine whether specific flag configurations improve or degrade measured performance,
 whether business metrics or system performance.
 
 ### Experimentation
 
-Tracking creates a crucial link between flag evaluations and business outcomes, enabling robust experimentation. Experimentation differs from generalized
-Performance Monitoring in its execution. The most common form of Experimentation being A/B testing which is when two variations of an application or feature
-are distributed randomly to similar groups and the differences in metrics is evaluated. For example, if a feature flag controls the order
-of items in a menu, tracking events can be emitted when users click on menu items. The feature flag provider can typically be set to distribute the different variations
+Tracking creates a crucial link between flag evaluations and business outcomes, enabling robust experimentation.
+Experimentation differs from generalized
+Performance Monitoring in its execution.
+The most common form of Experimentation being A/B testing which is when two variations of an application or feature
+are distributed randomly to similar groups and the differences in metrics is evaluated.
+For example, if a feature flag controls the order
+of items in a menu, tracking events can be emitted when users click on menu items.
+The feature flag provider can typically be set to distribute the different variations
 equally to your audience, making this an A/B test, helping to validate hypotheses about user behavior in a statistically relevant manner.
 
 ## Providers, Hooks and Integration
@@ -46,7 +51,8 @@ sequenceDiagram
 
 ## Track Event Implementation
 
-The `track` function requires only a label parameter. You don’t need to pass an identifier or flag evaluation context since the OpenFeature provider already maintains this information.
+The `track` function requires only a label parameter.
+You don’t need to pass an identifier or flag evaluation context since the OpenFeature provider already maintains this information.
 
 Optionally, you can associate additional metadata with each track event if your feature flagging tool supports it.
 
@@ -102,4 +108,4 @@ client.Track(
 
 </TabItem>
 
-</Tabs>
+</Tabs>

docs/tutorials/getting-started/dotnet.mdx

@@ -30,7 +30,8 @@ This walk-through assumes that:
 
 ### Step 1: Create a .NET 8 Web application
 
-To get started you can use the .NET SDK to initialise a web application. Open a terminal (**shell**, **Command Prompt**, or **bash**) and paste the following commands:
+To get started you can use the .NET SDK to initialise a web application.
+Open a terminal (**shell**, **Command Prompt**, or **bash**) and paste the following commands:
 
 ```shell
 dotnet new webapi -o openfeature-dotnet-sample
@@ -48,7 +49,8 @@ dotnet add package OpenFeature
 
 ### Step 3: Add code
 
-The following will initialise an `InMemoryProvider` for use within the web application. Open a code editor and add the C# code below to the Program.cs.
+The following will initialise an `InMemoryProvider` for use within the web application.
+Open a code editor and add the C# code below to the Program.cs.
 
 ```csharp
 // diff-add-block-start
@@ -135,9 +137,14 @@ dotnet build
 dotnet run
 ```
 
-In the logs you should see a line with the following `Now listening on: http://localhost:5251`, although the port number may differ. You can visit the following URL in your browser [http://localhost:5251/hello](http://localhost:5251/hello) (adjust port number as necessary) to view the hello world message. You should see the message "Hello!".
+In the logs you should see a line with the following `Now listening on: http://localhost:5251`, although the port number may differ.
+You can visit the following URL in your browser [http://localhost:5251/hello](http://localhost:5251/hello) (adjust port number as necessary) to view the hello world message.
+You should see the message "Hello!".
 
-"Why I'm I seeing that value?", you may ask. Well, it's because a provider hasn't been configured yet. Without a provider to actually evaluate flags, OpenFeature will return the default value. In the next step, you'll learn how to add a provider.
+"Why I'm I seeing that value?", you may ask.
+Well, it's because a provider hasn't been configured yet.
+Without a provider to actually evaluate flags, OpenFeature will return the default value.
+In the next step, you'll learn how to add a provider.
 
 ### Step 5: Configure a provider (flagd)
 
@@ -208,7 +215,8 @@ dotnet build
 dotnet run
 ```
 
-You can visit the following URL in your browser [http://localhost:5251/hello](http://localhost:5251/hello) (adjust port number as necessary) to view the hello world message. You should see the message "Hello!".
+You can visit the following URL in your browser [http://localhost:5251/hello](http://localhost:5251/hello) (adjust port number as necessary) to view the hello world message.
+You should see the message "Hello!".
 
 <FlagdChangeContent/>
 

docs/tutorials/getting-started/go.mdx

@@ -198,12 +198,12 @@ The complete `main.go` file is given below:
 package main
 
 import (
-	"context"
-	"log"
-	"net/http"
-	"github.com/gin-gonic/gin"
-	flagd "github.com/open-feature/go-sdk-contrib/providers/flagd/pkg"
-	"github.com/open-feature/go-sdk/openfeature"
+    "context"
+    "log"
+    "net/http"
+    "github.com/gin-gonic/gin"
+    flagd "github.com/open-feature/go-sdk-contrib/providers/flagd/pkg"
+    "github.com/open-feature/go-sdk/openfeature"
 )
 
 const defaultMessage = "Hello!"

docs/tutorials/getting-started/python.mdx

@@ -7,7 +7,6 @@ import FlagdContent from '@site/src/components/custom/tutorial/flagd-content.mdx
 import FlagdChangeContent from '@site/src/components/custom/tutorial/flagd-change-content.mdx';
 import WhyDefaultContent from '@site/src/components/custom/tutorial/why-default-content.mdx';
 
-
 # Getting Started with the OpenFeature Python SDK
 
 ## Introduction
@@ -67,6 +66,7 @@ pip install openfeature-provider-flagd
 ```
 
 Update `app.py` to import the SDK.
+
 ```python
   from openfeature import api
   from openfeature.contrib.provider.flagd import FlagdProvider
@@ -94,6 +94,7 @@ def index():
 ```
 
 ### Step 4: Run the application
+
 Let's start the app and see it in action, use the final code below.
 
 ```python
@@ -114,6 +115,7 @@ def index():
 
     return "Flask Server"
 ```
+
 Run the following command to start the server.
 
 ```sh
@@ -131,8 +133,9 @@ If all goes as planned, you should see "Flask Server".
 
 <FlagdContent />
 
-Flagd can be run as a [standalone binary](https://flagd.dev/reference/flagd-cli/flagd/) or [Kubernetes Operator](https://openfeature.dev/docs/tutorials/ofo/) 
-as well. If you don't have docker installed, get and install the [Flagd binary](https://github.com/open-feature/flagd/releases).
+Flagd can be run as a [standalone binary](https://flagd.dev/reference/flagd-cli/flagd/) or [Kubernetes Operator](https://openfeature.dev/docs/tutorials/ofo/)
+as well.
+If you don't have docker installed, get and install the [Flagd binary](https://github.com/open-feature/flagd/releases).
 With the flagd configuration in place, start flagd service with the following command.
 
 ```sh
@@ -143,7 +146,6 @@ flagd start -f file:flags.flagd.json
 
 Now that everything is in place, let's start the app again.
 
-
 ```sh
 flask run
 ```
@@ -162,6 +164,5 @@ This walk-through introduced you to the OpenFeature Python SDK.
 It covered how a provider can be configured to perform the flag evaluation and introduced basic feature flagging concepts.
 It also showcased how feature flags can be updated at runtime, without requiring a redeployment.
 
-[learn-flask]: https://flask.palletsprojects.com/en/3.0.x/
 [docker-download]: https://docs.docker.com/engine/install/
 [flag-key]: /specification/glossary#flag-key

docs/tutorials/getting-started/rust.mdx

@@ -10,7 +10,8 @@ import FlagdChangeContent from '@site/src/components/custom/tutorial/flagd-chang
 
 ## Introduction
 
-This tutorial explains how to integrate the OpenFeature Rust SDK into an Axum application using the flagd provider. In this guide you will learn how to:
+This tutorial explains how to integrate the OpenFeature Rust SDK into an Axum application using the flagd provider.
+In this guide you will learn how to:
 
 - Create a new Rust project with Cargo
 - Update dependencies to include Docker-based flagd configuration
@@ -56,7 +57,9 @@ Adjust version numbers according to the latest releases.
 
 ### Step 3: Set Up the Application
 
-Create or modify your `src/main.rs` with the following code. Notice the diff markers to indicate new additions:
+Create or modify your `src/main.rs` with the following code.
+Notice the diff markers to indicate new additions:
+
 ```rust
 // diff-remove-block-start
 fn main() {
@@ -131,8 +134,9 @@ async fn main() {
 
 <FlagdContent />
 
-Flagd can be run as a [standalone binary](https://flagd.dev/reference/flagd-cli/flagd/) or [Kubernetes Operator](https://openfeature.dev/docs/tutorials/ofo/) 
-as well. If you don't have docker installed, get and install the [Flagd binary](https://github.com/open-feature/flagd/releases).
+Flagd can be run as a [standalone binary](https://flagd.dev/reference/flagd-cli/flagd/) or [Kubernetes Operator](https://openfeature.dev/docs/tutorials/ofo/)
+as well.
+If you don't have docker installed, get and install the [Flagd binary](https://github.com/open-feature/flagd/releases).
 With the flagd configuration in place, start flagd service with the following command.
 
 ```sh
@@ -157,7 +161,7 @@ You should now be greeted with `Hello, welcome to this OpenFeature-enabled websi
 
 ## Conclusion
 
-This tutorial demonstrated how to integrate the OpenFeature Rust SDK with an Axum web server using a custom AppState containing a FlagdProvider. By leveraging flagd service, you can dynamically update feature flags at runtime without needing to redeploy your application.
+This tutorial demonstrated how to integrate the OpenFeature Rust SDK with an Axum web server using a custom AppState containing a FlagdProvider.
+By leveraging flagd service, you can dynamically update feature flags at runtime without needing to redeploy your application.
 
 For advanced configuration and more details, refer to the [OpenFeature Rust SDK documentation](https://docs.rs/open-feature-flagd/latest/open_feature_flagd/).
-

docs/tutorials/open-feature-cli.md

@@ -349,7 +349,8 @@ generate:
 
 ## Next Steps
 
-Want to dive deeper? Here are some great next steps:
+Want to dive deeper?
+Here are some great next steps:
 
 - Explore more generators: Try `openfeature generate` to see all supported languages
 - Set up provider integration: Connect your generated code to a real feature flag service using [OpenFeature providers](/ecosystem?instant_search%5BrefinementList%5D%5Btype%5D%5B0%5D=Provider)