From ad5062d3ead09c6a7ac0896452c4000b9b00d11f Mon Sep 17 00:00:00 2001 From: Santino Valenzuela <41457708+valenzsa@users.noreply.github.com> Date: Sun, 11 Nov 2018 21:23:27 -0500 Subject: [PATCH] Fixes several typos. (#22998) --- guide/english/agile/behavior-driven-development/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guide/english/agile/behavior-driven-development/index.md b/guide/english/agile/behavior-driven-development/index.md index f4c5efcb08..d64679038a 100644 --- a/guide/english/agile/behavior-driven-development/index.md +++ b/guide/english/agile/behavior-driven-development/index.md @@ -46,15 +46,15 @@ When he returns the blue garment for a replacement in black Then I should have three blue garments in stock And two black garments in stock. ``` -Along with it are some Benefites: +Along with it are some Benefits: 1. All development work can be traced back directly to business objectives. 2. Software development meets user need. Satisfied users = good business. -3. Efficient prioritisation - business-critical features are delivered first. +3. Efficient prioritization - business-critical features are delivered first. 4. All parties have a shared understanding of the project and can be involved in the communication. 5. A shared language ensures everyone (technical or not) has thorough visibility into the project’s progression. 6. Resulting software design that matches existing and supports upcoming business needs. -7. Improved quality code reducing costs of maintenance and minimising project risk. +7. Improved quality code reducing costs of maintenance and minimizing project risk. ## More Information * Wiki on BDD