diff --git a/content/en/blog/_posts/2020-04-21-contributor-communication-upstream-marketing.md b/content/en/blog/_posts/2020-04-21-contributor-communication-upstream-marketing.md
index 9d537b0a4d..3867c492bc 100644
--- a/content/en/blog/_posts/2020-04-21-contributor-communication-upstream-marketing.md
+++ b/content/en/blog/_posts/2020-04-21-contributor-communication-upstream-marketing.md
@@ -35,7 +35,7 @@ All of these numbers are only growing in scale, and with that comes the need to
 
 ## How we got here
 
-Kubernetes (k8s for short) communication grew out of a need for people
+Kubernetes (K8s for short) communication grew out of a need for people
 to connect in our growing community. With the best of intentions, the
 community spun up channels for people to connect. This energy was part
 of what helped Kubernetes grow so fast, and it also had us in sprawling out far and wide. As adoption grew, [contributors knew there was a need for standardization](https://github.com/kubernetes/community/issues/2466).
@@ -124,4 +124,4 @@ Reach out at one of the contact methods listed on [our README](https://github.co
 [repositories of amazing documentation]: http://github.com/kubernetes/community
 [meetings]: https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America%2FLos_Angeles
 [recorded code deep dives]: https://www.youtube.com/watch?v=yqB_le-N6EE
-[charter]: https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md
\ No newline at end of file
+[charter]: https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md