From 0bc39aa27a0c55e4737a42aebd19fd361552488d Mon Sep 17 00:00:00 2001 From: Quinn Slack Date: Mon, 21 Dec 2020 20:46:53 -0800 Subject: [PATCH] fix anchor link to "What's next" heading in operator docs --- content/en/docs/concepts/extend-kubernetes/operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/extend-kubernetes/operator.md b/content/en/docs/concepts/extend-kubernetes/operator.md index 140cf2557a..0e9d227a53 100644 --- a/content/en/docs/concepts/extend-kubernetes/operator.md +++ b/content/en/docs/concepts/extend-kubernetes/operator.md @@ -103,7 +103,7 @@ as well as keeping the existing service in good shape. ## Writing your own Operator {#writing-operator} If there isn't an Operator in the ecosystem that implements the behavior you -want, you can code your own. In [What's next](#whats-next) you'll find a few +want, you can code your own. In [What's next](#what-s-next) you'll find a few links to libraries and tools you can use to write your own cloud native Operator.