diff --git a/docs/concepts/workloads/controllers/deployment.md b/docs/concepts/workloads/controllers/deployment.md
index be776f87a2622..f2c16958ee1a2 100644
--- a/docs/concepts/workloads/controllers/deployment.md
+++ b/docs/concepts/workloads/controllers/deployment.md
@@ -18,7 +18,7 @@ You only need to describe the desired state in a Deployment object, and the Depl
 change the actual state to the desired state at a controlled rate for you. You can define Deployments to
 create new ReplicaSets, or remove existing Deployments and adopt all of their resources with new Deployments.
 
-**Note** You should not manage ReplicaSets owned by a Deployment, otherwise you are racing with the Deployment
+**Note:** You should not manage ReplicaSets owned by a Deployment, otherwise you are racing with the Deployment
 controller! All of the use cases should be covered just by manipulating the Deployment object. Consider opening
 an issue in the main Kubernetes repository, if your use case is not covered below.