From 4a1d20e8a370c040adffa33436e1ccd8ef224c6a Mon Sep 17 00:00:00 2001 From: Vyacheslav Matyukhin Date: Wed, 12 Feb 2020 16:26:05 +0300 Subject: [PATCH] Fix formatting in "Kubernetes Namespace" block --- docs/content/middlewares/overview.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/content/middlewares/overview.md b/docs/content/middlewares/overview.md index 71d16ac7a..376169776 100644 --- a/docs/content/middlewares/overview.md +++ b/docs/content/middlewares/overview.md @@ -143,11 +143,11 @@ then you'll have to append to the middleware name, the `@` separator, followed b !!! important "Kubernetes Namespace" - As Kubernetes also has its own notion of namespace, one should not confuse the "provider namespace" -with the "kubernetes namespace" of a resource when in the context of a cross-provider usage. -In this case, since the definition of the middleware is not in kubernetes, -specifying a "kubernetes namespace" when referring to the resource does not make any sense, -and therefore this specification would be ignored even if present. + As Kubernetes also has its own notion of namespace, one should not confuse the "provider namespace" + with the "kubernetes namespace" of a resource when in the context of a cross-provider usage. + In this case, since the definition of the middleware is not in kubernetes, + specifying a "kubernetes namespace" when referring to the resource does not make any sense, + and therefore this specification would be ignored even if present. !!! abstract "Referencing a Middleware from Another Provider"