diff --git a/public/_redirects b/public/_redirects
index 84f4ca02..d0d1d6f1 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -136,7 +136,7 @@
 /user-guide/aws/s3/ /aws/services/s3 301
 /user-guide/lambda-tools/vscode-extension/ /aws/tooling/lambda-tools/vscode-extension 301
 /user-guide/chaos-engineering/ /aws/capabilities/chaos-engineering/ 301
-/persistence/supported/ /aws/capabilities/state-management/persistence-coverage 301
+/persistence/supported/ /aws/capabilities/state-management/persistence 301
 /user-guide/aws/ce/ /aws/services/ce 301
 /user-guide/aws/kinesisanalyticsv2/ /aws/services/kinesisanalyticsv2 301
 /user-guide/state-management/cloud-pods/ /aws/capabilities/state-management/cloud-pods 301
@@ -546,7 +546,7 @@
 /user-guide/aws/s3 /aws/services/s3 301
 /user-guide/lambda-tools/vscode-extension /aws/tooling/lambda-tools/vscode-extension 301
 /user-guide/chaos-engineering /aws/capabilities/chaos-engineering/ 301
-/persistence/supported /aws/capabilities/state-management/persistence-coverage 301
+/persistence/supported /aws/capabilities/state-management/persistence 301
 /user-guide/aws/ce /aws/services/ce 301
 /user-guide/aws/kinesisanalyticsv2 /aws/services/kinesisanalyticsv2 301
 /user-guide/state-management/cloud-pods /aws/capabilities/state-management/cloud-pods 301
diff --git a/src/content/docs/aws/capabilities/state-management/persistence-coverage.mdx b/src/content/docs/aws/capabilities/state-management/persistence-coverage.mdx
deleted file mode 100644
index ed7e8974..00000000
--- a/src/content/docs/aws/capabilities/state-management/persistence-coverage.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Persistence Coverage
-description: Overview of the persistence coverage across the implemented AWS services.
-template: doc
-sidebar:
-    order: 7
-tags: ["Base"]
----
-
-import PersistenceCoverage from '../../../../../components/persistence-coverage/PersistenceCoverage.tsx';
-
-## Persistence Coverage Overview
-
-<PersistenceCoverage client:load />
-
-### Terminology
-
-- **Persistence Test Suite**: tested by LocalStack's internal persistence test suite.
-To test persistence, we use an approach similar to snapshot parity test:
-we first record API responses from LocalStack, we then reset and restore the snapshotted state,
-and finally verify that the same API responses matches with the initial ones.
diff --git a/src/content/docs/aws/capabilities/state-management/persistence.mdx b/src/content/docs/aws/capabilities/state-management/persistence.mdx
index a230b930..a922eea0 100644
--- a/src/content/docs/aws/capabilities/state-management/persistence.mdx
+++ b/src/content/docs/aws/capabilities/state-management/persistence.mdx
@@ -120,7 +120,7 @@ curl -X POST localhost:4566/_localstack/state/save
 
 Although we are working to support both snapshot-based persistence and Cloud pods for all AWS services,
 there are some common issues, known limitations, and also services that are not well tested for persistence support.
-An overview is available [here](/aws/capabilities/state-management/persistence-coverage).
+An overview is available [here](#persistence-coverage-overview).
 
 Please help us improve persistence support by reporting bugs on our [GitHub issue tracker](https://github.com/localstack/localstack/issues/new/choose).
 
@@ -159,4 +159,14 @@ When we restore server backends (like an RDS server or DynamoDB server), we make
 When LocalStack saves snapshots, it has to lock the particular service to avoid state pollution.
 That means that, while a snapshot for a particular service is created, all requests to the service are blocked.
 Depending on what you are building, you may find this behavior is slowing down your application.
-In most cases, the `ON_SHUTDOWN` save strategy should solve this problem.
\ No newline at end of file
+In most cases, the `ON_SHUTDOWN` save strategy should solve this problem.
+
+import PersistenceCoverage from '../../../../../components/persistence-coverage/PersistenceCoverage.tsx';
+
+## Persistence Coverage Overview
+
+<PersistenceCoverage client:load />
+
+### Terminology
+
+- **Persistence Test Suite**: tested by LocalStack's internal persistence test suite. To test persistence, we use an approach similar to snapshot parity testing. First, we record API responses from LocalStack, then we reset and restore the snapshotted state, and finally, we verify that the same API responses matches with the initial ones.