From e7447af5738e9f9a77a090e8b821e6ae9f17726b Mon Sep 17 00:00:00 2001
From: trungqudinh <44312665+trungqudinh@users.noreply.github.com>
Date: Fri, 7 Dec 2018 15:57:29 +0700
Subject: [PATCH] Fixed markdown syntax of Sprint docs (#24109)

Missing white space after the hyphen made a wrong rendering html.
---
 guide/english/agile/sprints/index.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/guide/english/agile/sprints/index.md b/guide/english/agile/sprints/index.md
index f0b9ad85dd..c725504fe9 100644
--- a/guide/english/agile/sprints/index.md
+++ b/guide/english/agile/sprints/index.md
@@ -6,7 +6,8 @@ title: Sprints
 In Scrum, the **Sprint** is a period of working time usually between one and four weeks in which the delivery team works on your project. Sprints are iterative, and continue until the project is completed. Each sprint begins with a Sprint Planning session, and ends with Sprint Review and Retrospective meetings. Using sprints, as opposed to months-long waterfall or linear sequential development methodologies, allows regular feedback loops between project owners and stakeholders on the output from the delivery team.
 
 ## Properties of a Sprint
-- A sprint should not be terminated prematurely if at all possible. If the stories within the sprint become obsolete, the team may decide to close them and pull new stories off of the product backlog. 
+
+- A sprint should not be terminated prematurely if at all possible. If the stories within the sprint become obsolete, the team may decide to close them and pull new stories off of the product backlog.
 - The team works to break up the User Stories to a size that can be completed within the duration of the Sprint without carrying over to the next. 
 - "Sprint" and "Iteration" are often used interchangeably.