diff --git a/content/en/blog/_posts/2021-02-27-annotating-k8s-for-humans.md b/content/en/blog/_posts/2021-02-27-annotating-k8s-for-humans.md
index 1c05fe2410..87af6e8863 100644
--- a/content/en/blog/_posts/2021-02-27-annotating-k8s-for-humans.md
+++ b/content/en/blog/_posts/2021-02-27-annotating-k8s-for-humans.md
@@ -11,7 +11,7 @@ Have you ever been asked to troubleshoot a failing Kubernetes service and strugg
 
 One of the problems as Kubernetes applications grow is the proliferation of services. As the number of services grows, developers start to specialize working with specific services. When it comes to troubleshooting, however, developers need to be able to find the source, understand the service and dependencies, and chat with the owning team for any service.
 
-## Human Service Discovery
+## Human service discovery
 
 Troubleshooting always begins with information gathering. While much attention has been paid to centralizing machine data (e.g., logs, metrics), much less attention has been given to the human aspect of service discovery. Who owns a particular service? What Slack channel does the team work on? Where is the source for the service? What issues are currently known and being tracked?