diff --git a/docs/content/routing/providers/kubernetes-crd.md b/docs/content/routing/providers/kubernetes-crd.md
index 96b192daf..a8654701a 100644
--- a/docs/content/routing/providers/kubernetes-crd.md
+++ b/docs/content/routing/providers/kubernetes-crd.md
@@ -110,9 +110,9 @@ spec:
 !!! important "Cross-provider namespace"
 
 	As Kubernetes also has its own notion of namespace, one should not confuse the kubernetes namespace of a resource
-(in the reference to the middleware) with the [provider namespace](../../middlewares/overview.md#provider-namespace),
-when the definition of the middleware is from another provider.
-In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored.
+	(in the reference to the middleware) with the [provider namespace](../../middlewares/overview.md#provider-namespace),
+	when the definition of the middleware is from another provider.
+	In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored.
 
 More information about available middlewares in the dedicated [middlewares section](../../middlewares/overview.md).
 
@@ -163,9 +163,9 @@ spec:
     If the optional `namespace` attribute is not set, the configuration will be applied with the namespace of the IngressRoute.
 
 	Additionally, when the definition of the TLS option is from another provider,
-the cross-provider syntax (`middlewarename@provider`) should be used to refer to the TLS option,
-just as in the [middleware case](../../middlewares/overview.md#provider-namespace).
-Specifying a namespace attribute in this case would not make any sense, and will be ignored.
+	the cross-provider syntax (`middlewarename@provider`) should be used to refer to the TLS option,
+	just as in the [middleware case](../../middlewares/overview.md#provider-namespace).
+	Specifying a namespace attribute in this case would not make any sense, and will be ignored.
 
 ### TLS