From 586081ad48e52395ad418a10be95ae6ebfd04c5c Mon Sep 17 00:00:00 2001
From: fgogolli <flamur.gogolli@gmail.com>
Date: Sun, 27 Aug 2017 11:05:17 +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 c0230bb167..da1169df6d 100644
--- a/docs/concepts/workloads/controllers/deployment.md
+++ b/docs/concepts/workloads/controllers/deployment.md
@@ -262,7 +262,7 @@ removed label still exists in any existing Pods and ReplicaSets.
 
 Sometimes you may want to rollback a Deployment; for example, when the Deployment is not stable, such as crash looping.
 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]).
+(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
 new revision is created if and only if the Deployment's pod template (`.spec.template`) is changed,