diff --git a/docs/docs/connectors/custom-connectors.mdx b/docs/docs/connectors/custom-connectors.mdx
index ec03bde78da6..ed6f60c3a699 100644
--- a/docs/docs/connectors/custom-connectors.mdx
+++ b/docs/docs/connectors/custom-connectors.mdx
@@ -48,7 +48,7 @@ the host and port with the appropriate values from your running Rasa X or Rasa O
 ## The `blueprint` method
 
 The `blueprint` method
-needs to create a [sanic blueprint](https://sanic.readthedocs.io/en/stable/sanic/blueprints.html#blueprints)
+needs to create a [sanic blueprint](https://sanicframework.org/en/guide/best-practices/blueprints.html#overview)
 that can be attached to a sanic server. 
 Your blueprint should have at least the two routes: `health` on the route `/`,
 and `receive` on the route `/webhook` (see example custom channel below).
diff --git a/docs/docs/http-api.mdx b/docs/docs/http-api.mdx
index c028ce90bcdf..d9a09dd8c3dc 100644
--- a/docs/docs/http-api.mdx
+++ b/docs/docs/http-api.mdx
@@ -39,7 +39,7 @@ By default, the HTTP server runs as a single process. You can change the number
 of worker processes using the `SANIC_WORKERS` environment variable. It is
 recommended that you set the number of workers to the number of available CPU cores
 (check out the
-[Sanic docs](https://sanic.readthedocs.io/en/stable/sanic/deploying.html#workers)
+[Sanic docs](https://sanicframework.org/en/guide/deployment/running.html#workers)
 for more details). This will only work in combination with the
 `RedisLockStore` (see [Lock Stores](./lock-stores.mdx).
 
@@ -118,3 +118,4 @@ The following is an example payload for a JWT token:
 ```
 
 To create and encode the token, you can use tools such as the [JWT Debugger](https://jwt.io/), or a Python module such as [PyJWT](https://pyjwt.readthedocs.io/en/latest/).
+
diff --git a/docs/docs/migration-guide.mdx b/docs/docs/migration-guide.mdx
index b1f98eabffc1..cfac39bd3ef2 100644
--- a/docs/docs/migration-guide.mdx
+++ b/docs/docs/migration-guide.mdx
@@ -1085,7 +1085,7 @@ model before trying to use it with this improved version.
 * The `--num_threads` parameter was removed from the `run` command. The
   server will always run single-threaded, but will now run asynchronously. If you want to
   make use of multiple processes, feel free to check out the [Sanic server
-  documentation](https://sanic.readthedocs.io/en/stable/sanic/deploying.html#running-via-gunicorn).
+  documentation](https://sanicframework.org/en/guide/deployment/running.html#gunicorn).
 
 * To avoid conflicts in script parameter names, connectors in the `run` command now need to be specified with
   `--connector`, as `-c` is no longer supported. The maximum history in the `rasa visualize` command needs to be