From 780d55c7e239891bd6902017d157dcecb4a14131 Mon Sep 17 00:00:00 2001 From: Hafid Feghouli Date: Sun, 14 Oct 2018 12:29:26 -0400 Subject: [PATCH] fix(documentation):added missing dot (#18533) Added missing dot "." at the end of the last sentence. --- .../src/pages/guide/english/agile/continuous-delivery/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/src/pages/guide/english/agile/continuous-delivery/index.md b/client/src/pages/guide/english/agile/continuous-delivery/index.md index e94d04dcd0c..c0fdd28ddef 100644 --- a/client/src/pages/guide/english/agile/continuous-delivery/index.md +++ b/client/src/pages/guide/english/agile/continuous-delivery/index.md @@ -5,7 +5,7 @@ title: Continuous Delivery Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.1 -It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery. Continuous delivery means that the team ensures every change can be deployed to production but may choose not to do it, usually due to business reasons +It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery. Continuous delivery means that the team ensures every change can be deployed to production but may choose not to do it, usually due to business reasons.