Merge pull request #1156 from stephenwade/patch-1

Correct spelling of "OAuth" in example

Author: janiceilene

contributing/localization-checklist.md

@@ -26,7 +26,7 @@ Use the following checklist to help make your files more translation-friendly. F
 | Guideline | Avoid | Use instead |
 | --------- | ----- | ----------- |
 | Avoid country specific information. | 800 numbers, addresses, etc. | If necessary, mention what countries the information applies to. |
-| Avoid the excessive use of stacked modifiers (Noun strings). This can lead to incorrect translations because it is not easy to tell what modifies what. | “public repository default source settings” or “Oauth app access restrictions” | "Default source settings for the public repository"  or "restrictions for Oath app access." If using a stacked modifier is essential, make sure the background information and context are clear so the linguist understands what is the noun that is being modified. |
+| Avoid the excessive use of stacked modifiers (Noun strings). This can lead to incorrect translations because it is not easy to tell what modifies what. | “public repository default source settings” or “OAuth app access restrictions” | "Default source settings for the public repository"  or "restrictions for OAuth app access." If using a stacked modifier is essential, make sure the background information and context are clear so the linguist understands what is the noun that is being modified. |
 | Avoid invisible plurals. | "Program update" or "File retrieval". Is this an update of one program or a general procedure for multiple programs?  For "File retrieval", Are you retrieving one file or all of them? | Write the sentence more clearly or provide additional context to eliminate ambiguity that can result in an incorrect translation. |
 | Avoid nominalization. | "To reach a conclusion" | Use "Conclude." |
 | Avoid using ambiguous modal auxiliary verbs. | May, might, ought, could, used to, etc. | Be more clear when writing to avoid ambiguity. |