From 2736c3603add3b3f3d8f13e1d44fe75cee2ae839 Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Fri, 3 Dec 2021 09:17:17 -0800 Subject: [PATCH] fix typo in doc --- site/content/docs/reference/code-walkthrough.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/docs/reference/code-walkthrough.md b/site/content/docs/reference/code-walkthrough.md index ec1551e5..98c9e0f0 100644 --- a/site/content/docs/reference/code-walkthrough.md +++ b/site/content/docs/reference/code-walkthrough.md @@ -210,7 +210,7 @@ The Kubernetes API groups used by the Pinniped CRDs and the Concierge's aggregat at install time. By default, everything is placed in the `*.pinniped.dev` group, for example one of the CRDs is `jwtauthenticators.authentication.concierge.pinniped.dev`. -Making this group name configurable is not a common pattern in Kubernetes apps, but is yields several advantages. +Making this group name configurable is not a common pattern in Kubernetes apps, but it yields several advantages. A discussion of this feature, including its implementation details, can be found in the [blog post for release v0.5.0](https://pinniped.dev/posts/multiple-pinnipeds/). Similar to leader election, much of this behavior is implemented in client middleware, and will not be obvious when reading the code.