Update navigation

website/docs/api-overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: Unleash Documentation
+title: API overview
 description: "Unleash is the largest open-source feature management platform. In our documentation, you’ll find everything from core Unleash concepts and feature flag best practices to detailed SDK and API guides—giving you all the resources you need to get the most out of Unleash."
 displayed_sidebar: documentation
 ---

website/docs/feature-flag-tutorials/use-cases/a-b-testing.md

@@ -1,11 +1,11 @@
 ---
-title: How to do A/B Testing using Feature Flags
+title: How to do A/B testing using feature flags
 slug: /feature-flag-tutorials/use-cases/a-b-testing
 ---
 
 Feature flags are a great way to run A/B or multivariate tests with minimal code modifications, and Unleash offers built-in features that make it easy to get started. In this tutorial, we will walk through how to do an A/B test using Unleash with your application.
 
-## How to Perform A/B Testing with Feature Flags
+## How to perform A/B testing with feature flags
 
 To follow along with this tutorial, you need access to an Unleash instance to create and manage feature flags. Head over to our [Quick Start documentation](/quickstart) for options, including running locally or using an [Unleash SaaS instance](https://www.getunleash.io/pricing?).
 
@@ -21,7 +21,7 @@ In this tutorial, you will learn how to set up and run an A/B test using feature
 
 You will also learn about how to [automate advanced A/B testing strategies](#multi-arm-bandit-tests-to-find-the-winning-variant) such as multi-arm bandit testing using feature flags.
 
-### Create a Feature Flag
+### Create a feature flag
 
 To do A/B testing, we'll create a feature flag to implement the rollout strategy. After that, we'll explore what strategies are and how they are configured in Unleash.
 
@@ -39,7 +39,7 @@ Once you have completed the form, click **Create feature flag**.
 
 Your new feature flag is now ready to be used. Next, we will configure the A/B testing strategy for your flag.
 
-### Target Users for A/B Testing
+### Target users for A/B testing
 
 With an A/B testing strategy, you’ll be able to:
 
@@ -93,13 +93,13 @@ Next, decide the percentage of users to target for each variant, known as the va
 
 ![You can configure multiple strategy variants for A/B testing within the gradual rollout form.](/img/use-case-experiment-variants.png)
 
-### Manage User Session Behavior
+### Manage user session behavior
 
 Unleash is built to give developers confidence in their ability to run A/B tests effectively. One critical component of implementing A/B testing strategies is maintaining a consistent experience for each user across multiple user sessions.
 
 For example, user `uuid1234` should be the target of `variantA` regardless of their session. The original subset of users that get `variantA` will continue to experience that variation of the feature over time. At Unleash, we call this [stickiness](/reference/stickiness). You can define the parameter of stickiness in the gradual rollout form. By default, stickiness is calculated by `sessionId` and `groupId`.
 
-### Track A/B Testing for your Key Performance Metrics
+### Track A/B testing for your key performance metrics
 
 An A/B testing strategy is most useful when you can track the results of a feature rollout to users. When your team has clearly defined the goals for your A/B tests, you can use Unleash to analyze how results tie back to key metrics, like conversion rates or time spent on a page. One way to collect this data is by enabling [impression data](/reference/impression-data) per feature flag. Impression data contains information about a specific feature flag activation check.
 
@@ -197,7 +197,7 @@ Here is an example of a payload that is returned from Google Analytics that incl
 
 By enabling impression data for your feature flag and listening to events within your application code, you can leverage this data flowing to your integrated analytics tools to make informed decisions faster and adjust your strategies based on real user behavior.
 
-### Roll Out the Winning Variant to All Users
+### Roll out the winning variant to all users
 
 After you have implemented your A/B test and measured the performance of a feature to a subset of users, you can decide which variant is the most optimal experience to roll out to all users in production.
 
@@ -207,11 +207,11 @@ When rolling out the winning variant, your flag may already be on in your produc
 
 After the flag has been available to 100% of users over time, archive the flag and clean up your codebase.
 
-## A/B Testing with Enterprise Automation
+## A/B testing with enterprise automation
 
 With Unleash, you can automate feature flags through APIs and even rely on [actions](/reference/actions) and [signals](/reference/signals) to enable and disable flags dynamically. When running A/B tests, you can configure your projects to execute tasks in response to application metrics and thresholds you define. For example, if an experimentation feature that targets a part of your user base logs errors, your actions can automatically disable the feature so your team is given the time to triage while still providing a seamless, alternative experience to users. Similarly, you can use the APIs to modify the percentage of users targeted for variations of a feature based off users engaging with one variation more than the other.
 
-### Multi-arm Bandit Tests to Find the Winning Variant
+### Multi-arm bandit tests to find the winning variant
 
 When running complex multivariate tests with numerous combinations, automating the process of finding the best variation of a feature is the most optimal, cost-effective approach for organizations with a large user base. [Multi-arm bandit tests](https://en.wikipedia.org/wiki/Multi-armed_bandit) are a powerful technique used in A/B testing to allocate traffic to different versions of a feature or application in a way that maximizes the desired outcome, such as conversion rate or click-through rate. This approach offers several advantages over traditional A/B testing and is a viable solution for large enterprise teams.
 

website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md

@@ -1,10 +1,10 @@
 ---
-title: How to Perform a Gradual Rollout
+title: How to perform a gradual rollout
 slug: /feature-flag-tutorials/use-cases/gradual-rollout
 pagination_next: feature-flag-tutorials/use-cases/a-b-testing
 ---
 
-## What is a Gradual Rollout?
+## What is a gradual rollout?
 
 A **gradual rollout** is a controlled release strategy where a new feature is first released to a small subset of users. This allows for monitoring user behavior, identifying potential issues, and gathering feedback before a full-scale launch. It also allows us to experiment quickly and safely.
 
@@ -14,7 +14,7 @@ Developers also use gradual rollouts to gather user feedback. Early adopters pro
 
 The key benefits of gradual rollouts are that you can experiment rapidly on a controlled group and roll back quickly if the experiment goes wrong. This reduces the risk of failure, improves software quality, improves user experience, and optimizes resource utilization.
 
-## How to Perform a Gradual Rollout with Unleash
+## How to perform a gradual rollout with Unleash
 
 To follow along with this tutorial, you will need an Unleash instance. If you’d prefer to self-host Unleash, read our [Quickstart guide](/quickstart). Alternatively, if you’d like your project to be hosted by Unleash, go to [getunleash.io](https://www.getunleash.io/pricing).
 
@@ -42,7 +42,7 @@ Your new feature flag has been created and is ready to be used. Upon returning t
 
 Next, we will configure the gradual rollout strategy for your new flag.
 
-## Implementing a Gradual Rollout Activation Strategy
+## Implementing a gradual rollout activation strategy
 
 An important Unleash concept that enables developers to perform a gradual rollout is an [activation strategy](/reference/activation-strategies). An activation strategy defines who will be exposed to a particular flag or flags. Unleash comes pre-configured with multiple activation strategies that let you enable a feature only for a specified audience, depending on the parameters under which you would like to release a feature.
 
@@ -76,7 +76,7 @@ Constraints and variants are not required for a gradual rollout. These additiona
 
 For gradual rollouts, _strategy constraints_ are most applicable for more granular conditions of a feature release. In the next section, we’ll explore how to apply a strategy constraint on top of a gradual rollout for more advanced use cases.
 
-## Applying Strategy Constraints
+## Applying strategy constraints
 
 When utilizing an activation strategy such as a gradual rollout, it may be necessary to further define which subset of users get access to a feature and when the rollout takes place, depending on the complexity of your use case. Unleash provides [strategy constraints](/reference/activation-strategies#constraints) as a way to fine-tune conditions under which a feature flag is evaluated.
 
@@ -95,11 +95,11 @@ Within a gradual rollout activation strategy, you can use strategy constraints t
 Add [constraints](/reference/activation-strategies#constraints) to refine the rollout based on user attributes, segments, or conditions.
 
 
-### Define Custom Context Fields for Strategy Constraints
+### Define custom context Fields for strategy constraints
 
 If you want to create new types of constraints that are not built into Unleash, you can create [custom context fields](/reference/unleash-context#custom-context-fields) to use in your gradual rollout for more advanced use cases.
 
-## Leveraging Segments
+## Using segments
 
 A [segment](/reference/segments) is a reusable collection of [strategy constraints](/reference/activation-strategies#constraints). Like with strategy constraints, you apply segments to feature flag activation strategies.
 
@@ -126,7 +126,7 @@ You must pass the relevant fields in your context in the SDK in order for gradua
 
 By following these steps and leveraging Unleash's features, you can effectively execute and refine gradual rollouts to minimize risks and optimize feature delivery.
 
-## Managing Gradual Rollouts With Enterprise Security In Mind
+## Managing gradual rollouts with enterprise security in mind
 
 For large-scale organizations, managing feature flags across many teams can be complex and challenging. Unleash was architected for your feature flag management to be scalable and traceable for enterprises, which boosts overall internal security posture while delivering software efficiently.
 
@@ -138,7 +138,7 @@ After you have implemented a gradual rollout strategy, we recommend managing the
 
 Read our documentation on how to effectively manage [feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale) while reducing security risks. Let’s walk through these recommended Unleash features in the subsequent sections.
 
-### Reviewing Application Metrics
+### Reviewing application metrics
 
 [Unleash metrics](/reference/api/unleash/metrics) are a great way to understand user traffic. With your application using feature flags, you can review:
 
@@ -150,7 +150,7 @@ Read our documentation on how to effectively manage [feature flags at scale](/to
 
 When managing a gradual rollout, leverage metrics to gain deeper insight into flag usage against your application over time. For large-scale organizations with many feature flags to manage, this can be a useful monitoring tool for individual flags you would like to keep track of.
 
-### Reviewing Audit Logs
+### Reviewing audit logs
 
 Because a feature flag service controls the way an application behaves in production, it can be highly important to have visibility into when changes have been made and by whom. This is especially true in highly regulated environments. In these cases, you might find audit logging useful for:
 
@@ -165,7 +165,7 @@ Unleash provides the data to log any change that has happened over time, at the
 
 Learn more about [Event Log](/reference/events#event-log) in our documentation.
 
-### Managing Change Requests
+### Managing change requests
 
 You can use Unleash's [change request](/reference/change-requests) feature to propose and review modifications to feature flags. This gives developers complete control over your production environment. In large scale organizations and heavily regulated industries, we want to help developers reduce risk of errors in production or making unwanted changes by team members that have not been properly reviewed and approved.
 

website/docs/feature-flag-tutorials/use-cases/how-to-create-feature-toggles.md

@@ -2,6 +2,7 @@
 title: Create a feature flag
 description: 'This guide shows you how to create feature flags in Unleash and how to add constraints, segments, variants, and more.'
 slug: /how-to-create-feature-flag
+pagination_next: how-to/how-to-schedule-feature-releases
 ---
 
 [Feature flags](../reference/feature-toggles) are a foundational component of Unleash, enabling you to manage features dynamically. This guide details the process of creating and configuring feature flags within Unleash. You'll learn how to create flags, define activation strategies, enable them, and optionally refine their behavior with constraints, segments, and variants.

website/docs/feature-flag-tutorials/use-cases/scaling-unleash.mdx

@@ -1,5 +1,5 @@
 ---
-title: Scaling Unleash for Enterprise Workloads
+title: Scaling Unleash for enterprise workloads
 ---
 
 import Tabs from '@theme/Tabs';

website/docs/feature-flag-tutorials/use-cases/security-compliance.md

@@ -1,5 +1,5 @@
 ---
-title: Feature Flag Security and Compliance for Enterprises
+title: Feature flag security and compliance for enterprises
 slug: /feature-flag-tutorials/use-cases/security-and-compliance
 ---
 

website/docs/feature-flag-tutorials/use-cases/trunk-based-development.md

@@ -1,5 +1,5 @@
 ---
-title: How to do Trunk-Based Development using Feature Flags
+title: How to do trunk-based development using feature flags
 slug: /feature-flag-tutorials/use-cases/trunk-based-development
 ---
 

website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md

@@ -1,5 +1,5 @@
 ---
-title: How to Implement User Management, Access Controls, and Auditing with Feature Flags
+title: How to implement user management, access controls, and auditing with feature flags
 slug: /feature-flag-tutorials/use-cases/user-management-access-controls-auditing
 ---
 

website/docs/how-to/how-to-setup-provisioning-with-okta.md

@@ -1,5 +1,6 @@
 ---
 title: Set up Okta provisioning
+pagination_next: how-to/how-to-setup-provisioning-with-okta
 ---
 
 :::note Availability

website/docs/reference/activation-strategies.md

@@ -1,5 +1,5 @@
 ---
-title: Activation Strategies
+title: Activation strategies
 ---
 
 import VideoContent from '@site/src/components/VideoContent.jsx'

website/docs/reference/api-tokens-and-client-keys.mdx

@@ -1,5 +1,5 @@
 ---
-title: API Tokens and Client Keys
+title: API tokens and client keys
 pagination_next: reference/front-end-api
 ---
 

website/docs/reference/change-requests.mdx

@@ -1,5 +1,5 @@
 ---
-title: Change Requests
+title: Change requests
 ---
 
 import VideoContent from '@site/src/components/VideoContent.jsx';

website/docs/reference/command-menu.md

@@ -1,5 +1,5 @@
 ---
-title: Command Menu
+title: Command menu
 ---
 
 :::note Availability

website/docs/reference/custom-activation-strategies.md

@@ -1,5 +1,5 @@
 ---
-title: Custom Activation Strategies
+title: Custom activation strategies
 ---
 
 :::caution

website/docs/reference/environment-import-export.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Import and Export'
+title: Import and export
 ---
 import ApiRequest from '@site/src/components/ApiRequest'
 

website/docs/reference/feature-toggle-variants.md

@@ -1,5 +1,5 @@
 ---
-title: Feature Flag Variants (deprecated)
+title: Feature flag variants (deprecated)
 ---
 :::warning
 

website/docs/reference/feature-toggles.mdx

@@ -1,5 +1,5 @@
 ---
-title: Feature Flags
+title: Feature flags
 pagination_next: reference/activation-strategies
 ---
 

website/docs/reference/impression-data.md

@@ -1,5 +1,5 @@
 ---
-title: Impression Data
+title: Impression data
 pagination_next: reference/events
 ---
 

website/docs/reference/login-history.mdx

@@ -1,5 +1,5 @@
 ---
-title: Login History
+title: Login history
 ---
 
 :::note Availability

website/docs/reference/maintenance-mode.mdx

@@ -1,5 +1,5 @@
 ---
-title: Maintenance Mode
+title: Maintenance mode
 ---
 
 :::note Availability

website/docs/reference/project-collaboration-mode.md

@@ -1,5 +1,5 @@
 ---
-title: Project Collaboration Mode
+title: Project collaboration mode
 ---
 
 :::note Availability

website/docs/reference/public-signup.mdx

@@ -1,5 +1,5 @@
 ---
-title: Public Invite Links
+title: Public invite links
 ---
 
 Public invite links allow you to invite new team members to your Unleash instance. Any user who receives an invite link can use it to sign up for the Unleash instance that generated the link. When users sign up using an invite link, they are automatically assigned the [Viewer](../reference/rbac.md#predefined-roles) role.

website/docs/reference/rbac.md

@@ -1,6 +1,6 @@
 ---
 id: rbac
-title: Role-based Access Control
+title: Role-based access control
 ---
 
 :::note Availability

website/docs/reference/resource-limits.mdx

@@ -1,5 +1,5 @@
 ---
-title: Resource Limits
+title: Resource limits
 ---
 
 :::note Availability

website/docs/reference/service-accounts.md

@@ -1,5 +1,5 @@
 ---
-title: Service Accounts
+title: Service accounts
 ---
 
 :::note Availability

website/docs/reference/strategy-variants.mdx

@@ -1,5 +1,5 @@
 ---
-title: Strategy Variants
+title: Strategy variants
 ---
 
 import VideoContent from '@site/src/components/VideoContent.jsx'

website/docs/reference/technical-debt.md

@@ -1,5 +1,5 @@
 ---
-title: Technical Debt
+title: Technical debt
 pagination_next: reference/insights
 ---
 

website/docs/reference/unleash-context.md

@@ -1,8 +1,8 @@
 ---
-title: Unleash Context
+title: Unleash context
 ---
 
-The **Unleash Context** contains information related to the current feature flag request. Unleash uses this context to evaluate [activation strategies](activation-strategies) and [strategy constraints](../reference/activation-strategies#constraints) and to calculate [flag stickiness](../reference/stickiness). The Unleash Context is an important feature of all the [Unleash client SDKs](../reference/sdks).
+The **Unleash context** contains information related to the current feature flag request. Unleash uses this context to evaluate [activation strategies](activation-strategies) and [strategy constraints](../reference/activation-strategies#constraints) and to calculate [flag stickiness](../reference/stickiness). The Unleash Context is an important feature of all the [Unleash client SDKs](../reference/sdks).
 
 ## Overview
 

website/docs/topics/feature-flags/feature-flag-best-practices.mdx

@@ -2,6 +2,7 @@
 title: "11 principles for building and scaling feature flag systems"
 description: Build a scalable, secure feature flag system with 11 key principles. Improve DevOps metrics, ensure reliability, and enhance developer experience."
 toc_max_heading_level: 2
+pagination_next: topics/feature-flags/best-practices-using-feature-flags-at-scale
 ---
 
 import VideoContent from '@site/src/components/VideoContent.jsx';

website/docs/topics/what-is-a-feature-flag.mdx

@@ -2,7 +2,7 @@
 title: What is a feature flag and why are feature flags used?
 slug: /what-is-a-feature-flag
 description: Feature flags let you control software features in real time, enabling safer deployments, better testing, and faster innovation.
-pagination_next: topics/feature-flags/feature-flag-best-practices
+pagination_next: understanding-unleash/the-anatomy-of-unleash
 ---
 
 Feature flags allow you to release, test, and manage features and functionality across your application without changing the source code. Organizations use added control and flexibility to deliver more and higher quality features with reduced cost, time, and risk.

website/docs/understanding-unleash/data-collection.md

@@ -1,5 +1,6 @@
 ---
 title: Data and privacy
+pagination_next: using-unleash/compliance/compliance-overview
 ---
 
 At Unleash, we prioritize the privacy and security of our customers' data. Our [architecture](/understanding-unleash/the-anatomy-of-unleash) ensures privacy by evaluating feature flags locally within the [client SDKs](/reference/sdks) or [Unleash Edge](/reference/unleash-edge), meaning no user data is shared with the Unleash instance.

website/docs/understanding-unleash/the-anatomy-of-unleash.mdx

@@ -1,5 +1,5 @@
 ---
-title: The Anatomy of Unleash
+title: Unleash fundamentals
 ---
 
 This guide's purpose is to give you a conceptual overview of how Unleash works. It covers the various components that exist within our system and how they interact with each other and with external applications. The diagrams help you understand the fundamental building blocks, such as [projects](../reference/projects), [environments](../reference/environments), [variants](../reference/strategy-variants) and of course, [feature flags](../reference/feature-toggles).