diff --git a/docs/docs/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop.mdx b/docs/docs/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop.mdx
index 08a8c99b23..a06d1a0c6c 100644
--- a/docs/docs/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop.mdx
+++ b/docs/docs/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop.mdx
@@ -33,11 +33,11 @@ The Tracetest GraphQL trigger enables you to unleash the power of the trace-base
 
 By creating a Tracetest GraphQL test, you will be able to create trace-based assertions to be applied across the entire flow like any other Tracetest test. Not only that but it allows you to mix and match it with your existing Monitors, Test Suites and CI/CD validations.
 
-Another big benefit of using traces as test specs is that you can:
+Other impactful benefits of using traces as test specs are:
 
-- Get faster MTTR for failing performance tests
-- Assert against the Mutiple Queries and Mutations at once from a single test execution
-- Validate functionality of other parts of your system that may be broken, even when the initial request is passing
+- Faster MTTR for failing performance tests.
+- Assert against the Mutiple Queries and Mutations at once from a single test execution.
+- Validate functionality of other parts of your system that may be broken, even when the initial request is passing.
 
 ## Requirements
 
diff --git a/examples/tracetest-jaeger-graphql-pokeshop/README.md b/examples/tracetest-jaeger-graphql-pokeshop/README.md
index 818884dd97..8897a04d14 100644
--- a/examples/tracetest-jaeger-graphql-pokeshop/README.md
+++ b/examples/tracetest-jaeger-graphql-pokeshop/README.md
@@ -1,14 +1,5 @@
 # Tracetest + Amazon X-Ray (using Tracetest awsxray integration) + Pokeshop
 
-> [Read the detailed recipe for setting up Tracetest + Amazon X-Ray (using Tracetest awsxray integration) + Pokeshop in our documentation.](https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-aws-x-ray-pokeshop)
+> [Read the detailed recipe for setting up Tracetest + Amazon X-Ray (using Tracetest awsxray integration) + Pokeshop in our documentation.](https://docs.tracetest.io/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop)
 
 This repository objective is to show how you can configure your Tracetest instance to connect to AWS X-Ray and use it as its tracing backend.
-
-## Steps
-
-1. [Install the tracetest CLI](https://docs.tracetest.io/installing/)
-2. Run `tracetest configure --server-url http://localhost:11633` on a terminal
-3. Update the `.env` file adding a valid set of AWS credentials
-4. Update the `tracetest.provision.yaml` file adding a valid set of AWS credentials
-5. Run the project by using docker-compose: `docker-compose up -d` (Linux) or `docker compose up -d` (Mac)
-6. Test if it works by running: `tracetest run test -f tests/test.yaml`. This would trigger a test that will send and retrieve spans from the X-Ray instance that is running on your machine.