diff --git a/docs/guide/fields.md b/docs/guide/fields.md
index acf8796b..8eaa9d1a 100644
--- a/docs/guide/fields.md
+++ b/docs/guide/fields.md
@@ -30,7 +30,7 @@ class Fruit2:
 > [!TIP]
 > For choices using
 > [Django's TextChoices/IntegerChoices](https://docs.djangoproject.com/en/4.2/ref/models/fields/#enumeration-types)
-> it is recommented using the [django-choices-field](/integrations/choices-field) integration
+> it is recommented using the [django-choices-field](../integrations/choices-field.md) integration
 > enum handling.
 
 ## Relationships
@@ -56,7 +56,7 @@ class Color:
 ```
 
 Note that all relations can naturally trigger the n+1 problem. To avoid that, you can either
-enable the [Optimizer Extension](../optimizer) which will automatically
+enable the [Optimizer Extension](./optimizer.md) which will automatically
 solve some general issues for you, or even use
 [Data Loaders](https://strawberry.rocks/docs/guides/dataloaders) for more complex
 situations.
diff --git a/docs/guide/filters.md b/docs/guide/filters.md
index d0a5d44d..bda6c92e 100644
--- a/docs/guide/filters.md
+++ b/docs/guide/filters.md
@@ -43,7 +43,7 @@ input FruitFilter {
 > [!TIP]
 > If you are using the [relay integration](relay.md) and working with types inheriting
 > from `relay.Node` and `GlobalID` for identifying objects, you might want to set
-> `MAP_AUTO_ID_AS_GLOBAL_ID=True` in your [strawberry django settings](../settings)
+> `MAP_AUTO_ID_AS_GLOBAL_ID=True` in your [strawberry django settings](./settings.md)
 > to make sure `auto` fields gets mapped to `GlobalID` on types and filters.
 
 ## AND, OR, NOT, DISTINCT ...
diff --git a/docs/guide/mutations.md b/docs/guide/mutations.md
index e0d592d6..c6df3586 100644
--- a/docs/guide/mutations.md
+++ b/docs/guide/mutations.md
@@ -15,7 +15,7 @@ Here are the differences between those:
 - Strawberry Django's mutation will be sure that the mutation is executed in an async safe
   environment, meaning that if you are running ASGI and you define a `sync` resolver, it will
   automatically be wrapped in a `sync_to_async` call.
-- It will better integrate with the [permissioning integration](../permissions)
+- It will better integrate with the [permission integration](./permissions.md)
 - It has an option to automatically handle common django errors and return them
   in a standardized way (more on that below)
 
diff --git a/docs/guide/pagination.md b/docs/guide/pagination.md
index caa6fc22..339c199a 100644
--- a/docs/guide/pagination.md
+++ b/docs/guide/pagination.md
@@ -28,4 +28,4 @@ There is not default limit defined. All elements are returned if no pagination l
 ## Relay pagination
 
 For more complex scenarios, a cursor pagination would be better. For this,
-use the [relay integration](../relay) to define those.
+use the [relay integration](./relay.md) to define those.
diff --git a/docs/integrations/guardian.md b/docs/integrations/guardian.md
index cb2bea33..a3661345 100644
--- a/docs/integrations/guardian.md
+++ b/docs/integrations/guardian.md
@@ -7,5 +7,5 @@ title: django-guardian
 This lib provides integration for per-object-permissions using
 [django-guardian](https://django-guardian.readthedocs.io/en/stable/).
 
-Check the [Permission Extension Guide](/references/permissions) for more information
+Check the [Permission Extension Guide](../guide/permissions.md) for more information
 on how to use it.