summaryrefslogtreecommitdiff
path: root/update-release-docs.md
diff options
context:
space:
mode:
authork8s-merge-robot <k8s.production.user@gmail.com>2016-02-18 10:29:49 -0800
committerk8s-merge-robot <k8s.production.user@gmail.com>2016-02-18 10:29:49 -0800
commit18f6071ac6ec53d1d2d743939ccc98f8ed2b9b73 (patch)
treee5ff07869a05b80a1ae8f16eaa5cd4a2b6a52389 /update-release-docs.md
parent3afcab08f26f2bb0977ad3703e10352792e15482 (diff)
parent024b847eb1f07f450008f6997cdff1f9233c7b01 (diff)
Merge pull request #21177 from laushinka/spelling-fixes
Auto commit by PR queue bot
Diffstat (limited to 'update-release-docs.md')
-rw-r--r--update-release-docs.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/update-release-docs.md b/update-release-docs.md
index e94c5442..e0c04047 100644
--- a/update-release-docs.md
+++ b/update-release-docs.md
@@ -104,7 +104,7 @@ The high level steps to update docs in an existing collection are:
## Updating docs on HEAD
[Development guide](development.md) provides general instructions on how to contribute to kubernetes github repo.
-[Docs how to guide](how-to-doc.md) provides conventions to follow while writting docs.
+[Docs how to guide](how-to-doc.md) provides conventions to follow while writing docs.
## Updating docs in release branch