From 1d11905cb5020f0675c7886db2bd51997f2ee83e Mon Sep 17 00:00:00 2001
From: fgogolli <flamur.gogolli@gmail.com>
Date: Sun, 27 Aug 2017 11:26:51 +0100
Subject: [PATCH] Update deployment.md

---
 docs/concepts/workloads/controllers/deployment.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts/workloads/controllers/deployment.md b/docs/concepts/workloads/controllers/deployment.md
index da1169df6d..acc21c984e 100644
--- a/docs/concepts/workloads/controllers/deployment.md
+++ b/docs/concepts/workloads/controllers/deployment.md
@@ -264,7 +264,7 @@ Sometimes you may want to rollback a Deployment; for example, when the Deploymen
 By default, all of the Deployment's rollout history is kept in the system so that you can rollback anytime you want
 (you can change that by modifying revision history limit).
 
-**Note:** a Deployment's revision is created when a Deployment's rollout is triggered. This means that the
+**Note:** A Deployment's revision is created when a Deployment's rollout is triggered. This means that the
 new revision is created if and only if the Deployment's pod template (`.spec.template`) is changed,
 for example if you update the labels or container images of the template. Other updates, such as scaling the Deployment,
 do not create a Deployment revision, so that we can facilitate simultaneous manual- or auto-scaling.