summaryrefslogtreecommitdiff
path: root/release-notes.md
diff options
context:
space:
mode:
authorPreet Bhinder <preet@apcera.com>2016-04-05 16:20:08 -0700
committerPreet Bhinder <preet@apcera.com>2016-04-05 16:20:08 -0700
commitb69bdf9103212003723e68ce4220d2240c00995a (patch)
tree6c54dbda3b09846e07d832facd87df7c8d8f7c85 /release-notes.md
parent6554050a293ce39a28239f2b34b0661b28748d5f (diff)
Fixed typo: kuberntes -> kubernetes
"Kubernetes" was misspelled in a couple of places.
Diffstat (limited to 'release-notes.md')
-rw-r--r--release-notes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/release-notes.md b/release-notes.md
index acc7c16b..a3cfa59e 100644
--- a/release-notes.md
+++ b/release-notes.md
@@ -132,7 +132,7 @@ With v1.2.0, the release notes were moved from their previous [github releases](
location to [CHANGELOG.md](../../CHANGELOG.md). Going forward this seems like a good plan.
Other projects do similarly.
-The kuberntes.tar.gz download link is also displayed along with the release notes
+The kubernetes.tar.gz download link is also displayed along with the release notes
in [CHANGELOG.md](../../CHANGELOG.md).
Is there any reason to continue publishing anything to github releases if