Minor protocol-detection doc tweak

Signed-off-by: Flynn <[email protected]>
linkerd · Dec 4, 2024 · 01a83fb · 01a83fb
1 parent 828abd1
commit 01a83fb
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/linkerd.io/content/2-edge/features/protocol-detection.md b/linkerd.io/content/2-edge/features/protocol-detection.md
@@ -107,9 +107,9 @@ provide will _replace_, not augment, the default list of opaque ports.
 
 {{< note >}}
 If you are using [authorization policies](../server-policy/), the `Server`'s
-`proxyProtocol` field which can be used to control protocol detection behavior
-and can be used instead of a Service annotation. Regardless, we suggest
-annotating the Service object for clarity.
+`proxyProtocol` field can be used to control protocol detection behavior
+instead of a Service annotation. Regardless, we suggest annotating the
+Service object for clarity.
 {{< /note >}}
 
 ## Marking ports as skip ports

diff --git a/linkerd.io/content/2.16/features/protocol-detection.md b/linkerd.io/content/2.16/features/protocol-detection.md
@@ -107,9 +107,9 @@ provide will _replace_, not augment, the default list of opaque ports.
 
 {{< note >}}
 If you are using [authorization policies](../server-policy/), the `Server`'s
-`proxyProtocol` field which can be used to control protocol detection behavior
-and can be used instead of a Service annotation. Regardless, we suggest
-annotating the Service object for clarity.
+`proxyProtocol` field can be used to control protocol detection behavior
+instead of a Service annotation. Regardless, we suggest annotating the
+Service object for clarity.
 {{< /note >}}
 
 ## Marking ports as skip ports