Edits to global-product-delivery.md (#320)

* Edits to global-product-delivery.md

Edited this topic in prep for featuring it on social media.

* Update global-product-delivery.md

Removed periods in list per review.

* Update global-product-delivery.md

Removed trailing spaces.

* Update software-internationalization.md

Removed trailing space.

globalization/methodology/global-product-delivery.md

@@ -7,11 +7,6 @@ ms.date: 6/7/2022
 
 # Global product delivery
 
-> If you talk to a man in a language he understands, that goes to his head.
-> If you talk to him in his language, that goes to his heart.
->
-> — Nelson Mandela
-
 A great global product has an experience that goes beyond the basic function of the product.
 As a customer, the product feels like it was created specifically for you, no matter where you live or the language you speak.
 It feels like it belongs to your culture, language, and region.
@@ -32,7 +27,7 @@ We all come with an intuitive sense of what is acceptable and expected based on
 The experiences of people elsewhere in the world can be remarkably different.
 Stereotypical, inauthentic, or lack of diverse representation can turn customers away.
 
-Consider these aspects, that may vary widely by locale and language:
+Consider the following aspects, which may vary widely by locale and language:
 
 * Access to technology and bandwidth.
 * Payment methods.
@@ -79,7 +74,7 @@ Certain features may be regulated or restricted, particularly encryption and ant
 ## Roles
 
 Delivering software products worldwide can be a complex process that involves many disciplines within an organization.
-Global product delivery can require awareness and participation from:
+Global product delivery can require awareness and participation from people in these roles:
 
 * Development
 * Content creation
@@ -94,10 +89,7 @@ See [Roles and responsibilities](roles-and-responsibilities.md)
 
 ## Start early
 
-When you build global awareness and localizability into your product and process as early as possible, you reduce risk and cost.
-
-In our experience, world-readiness can be quite challenging to retrofit to an existing application.
-For a pre-existing application, many components may need to be redesigned, particularly in the user interface.
+When you build global awareness and localizability into your product and process as early as possible, you reduce risk and cost. In our experience, world-readiness can be quite challenging to retrofit to an existing application. For a pre-existing application, many components may need to be redesigned, particularly in the user interface.
 
 Even if your initial release is in only one language, a world-ready application can reach more markets because it supports the local formatting conventions for calendar, date, time, numbers, and currency.
 When you're ready to localize into to more languages and markets, the cost is lower because your organization and the application are prepared.
@@ -110,20 +102,15 @@ When starting a project, it's vital to get these fundamentals in place as early
 
 2. Produce and test localized builds.
 
-   [Pseudolocalization](pseudolocalization.md) is an excellent strategy to enable build and test without the cost of translation.
+   [Pseudolocalization](pseudolocalization.md) is an excellent method to enable build and test without incurring the cost of translation.
 
 3. Validate the localization round-trip from development to translator and back.
-
    Perform an early pilot, perhaps with minimal content and only one or a few languages, to minimize surprises later.
 
 4. Implement the ability to choose the language and locale.
-
    Having a means to select the language and locale independently from the language and locale of the platform makes it easy to develop, test, and debug.
    Plus, it's a useful feature for multilingual users.
 
-This baseline should be maintained for the entire lifecycle of the product.
-
-Once you've set a strong baseline, you can start iterating.
-For each sprint or milestone, evaluate your status and progress by defining [exit criteria](exit-criteria.md).
+This baseline should be maintained for the entire lifecycle of the product. Once you've set a strong baseline, you can start iterating. For each sprint or milestone, evaluate your status and progress by defining [exit criteria](exit-criteria.md).
 
 For next steps, see [Global products and rapid development](rapid-development.md).