docs: remove extra diagram (#8203)

<!-- Thanks for creating a PR! To make it easier for reviewers and
everyone else to understand what your changes relate to, please add some
relevant content to the headings below. Feel free to ignore or delete
sections that you don't think are relevant. Thank you! ❤️ -->

## About the changes
<!-- Describe the changes introduced. What are they and why are they
being introduced? Feel free to also add screenshots or steps to view the
changes if they're visual. -->

<!-- Does it close an issue? Multiple? -->
Closes #

<!-- (For internal contributors): Does it relate to an issue on public
roadmap? -->
<!--
Relates to [roadmap](https://github.com/orgs/Unleash/projects/10) item:
#
-->

### Important files
<!-- PRs can contain a lot of changes, but not all changes are equally
important. Where should a reviewer start looking to get an overview of
the changes? Are any files particularly important? -->


## Discussion points
<!-- Anything about the PR you'd like to discuss before it gets merged?
Got any questions or doubts? -->

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

@@ -9,28 +9,13 @@ A **gradual rollout** is a controlled release strategy where a new feature is fi
 
 By exposing the new feature to a limited audience, potential issues, bugs, or performance bottlenecks can be detected and addressed early on, preventing widespread impact.
 
-This diagram below scopes out the process and structure of a gradual rollout implementation using Unleash. In this use case tutorial, you'll learn the recommended method of configuring a gradual rollout with your application and Unleash.
-
-![A breakdown of the entire scope of implementing a gradual rollout.](/img/tutorial-gradual-rollout-diagram.png)
-
 Developers also use gradual rollouts to gather user feedback. Early adopters provide valuable insights into user experience, usability, and feature effectiveness, enabling rapid improvements. Gradual rollouts are also significant for testing in production. Real-world usage patterns and performance can be monitored closely, helping to ensure the new release is ready for a broader user base.
 
 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
 
-In order to set up a gradual rollout, you will need:
-
--   A place to host a feature flag management service
--   An API Token
--   An application connected to an Unleash SDK
-
-In order to set up your systems to create and manage a gradual rollout, you’ll need to decide where to host a feature flag management service. This is a critical component of creating features that will hide behind a feature flag for a gradual rollout. There are two primary options for deciding where to host a service:
-
--   Self-hosted: Deploy Unleash on your infrastructure (e.g., Docker, Kubernetes)
--   Hosted by Unleash
-
-Follow our documentation on [Self-Hosting with Unleash](/using-unleash/deploy/getting-started) to get started using your infrastructure. Alternatively, read our [Quickstart documentation](/quickstart) if you’d like your project to be hosted by Unleash.
+To follow along with this tutorial, you will need an Unleash instance. Follow our documentation on [Self-Hosting with Unleash](/using-unleash/deploy/getting-started) to get started using your infrastructure. Alternatively, read our [Quickstart documentation](/quickstart) if you’d like your project to be hosted by Unleash.
 
 With Unleash set up, you can use your application to talk to Unleash through one of our SDKs.
 
@@ -88,13 +73,7 @@ Constraints and variants are not required for a gradual rollout. These additiona
 
 [Strategy variants](/reference/strategy-variants) can expose a particular version of a feature to select user bases when a flag is enabled. From there, a way to use the variants is to view the performance metrics and see which is more efficient. We can create several variations of this feature to release to users and gather performance metrics to determine which one yields better results.
 
-![List of activation strategies](/img/tutorial-activation-strategies-list.png)
-
-In the diagram above, we list and describe all the activation strategies Unleash offers. The default strategy and gradual rollout strategy are the only two that support _both_ variants and constraints. The remaining stategies can only add constraints.
-
-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.
+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