Typographical suggestions by @ashnazg

Author: navarr

proposed/internationalization-meta.md

@@ -2,7 +2,7 @@
 
 ## 1. Summary
 
-Developers of components that are not coupled to any specific framework often find themselves in need of displaying a message to the user of the web application. However, being as they are not a component of a specific framework - their options for making these messages localizable is limited. In many cases, developers will make no attempt to pass these messages through a localization layer.
+Developers of components that are not coupled to any specific framework often find themselves in need of displaying a message to the user of the web application. However, being as they are not a component of a specific framework, their options for making these messages localizable is limited. In many cases, developers will make no attempt to pass these messages through a localization layer.
 
 To resolve this issue and encourage the localization of libraries, a standard method for translating and transforming messages is necessary.
 
@@ -14,7 +14,7 @@ To resolve this issue and encourage the localization of libraries, a standard me
 
 ### 3.2. Non-Goals
 
-* This PSR does not provide a standard for the storage and management of translatable items and their translations. That is, this PSR is about denoting that a message is translateable - not providing the specific translations for it.
+* This PSR does not provide a standard for the storage and management of translatable items and their translations. That is, this PSR is about denoting that a _message is translatable_ - **not** providing the specific translations for it.
 * This PSR does not provide a mechanism for collecting translatable items from a component's source code.
 * This PSR only addresses text present in PHP code.  It is not concerned with the translation of user content stored in a database or similar data store.