Fix some brand names in the docs

README.md

@@ -15,7 +15,7 @@ This repo contains the source code and documentation powering [reactjs.org](http
 ### Installation
 
 1. `cd reactjs.org` to go into the project root
-1. `yarn` to install the website's NPM dependencies
+1. `yarn` to install the website's npm dependencies
 
 ### Running locally
 

content/docs/accessibility.md

@@ -263,7 +263,7 @@ VoiceOver is an integrated screen reader on Apple devices.
 Refer to the following guides on how activate and use VoiceOver:
 
 - [WebAIM - Using VoiceOver to Evaluate Web Accessibility](http://webaim.org/articles/voiceover/)
-- [Deque - VoiceOver for OSX Keyboard Shortcuts](https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts)
+- [Deque - VoiceOver for OS X Keyboard Shortcuts](https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts)
 - [Deque - VoiceOver for iOS Shortcuts](https://dequeuniversity.com/screenreaders/voiceover-ios-shortcuts)
 
 #### JAWS in Internet Explorer

content/warnings/refs-must-have-owner.md

@@ -19,7 +19,7 @@ You are probably here because you got one of the following error messages:
 This usually means one of two things:
 
 - You are trying to add a `ref` to an element that is being created outside of a component's render() function.
-- You have multiple (conflicting) copies of React loaded (eg. due to a misconfigured NPM dependency)
+- You have multiple (conflicting) copies of React loaded (eg. due to a misconfigured npm dependency)
 
 
 ## Invalid Refs
@@ -28,6 +28,6 @@ Only a ReactOwner can have refs. This usually means that you're trying to add a
 
 ## Multiple copies of React
 
-Bower does a good job of deduplicating dependencies, but NPM does not. If you aren't doing anything (fancy) with refs, there is a good chance that the problem is not with your refs, but rather an issue with having multiple copies of React loaded into your project. Sometimes, when you pull in a third-party module via npm, you will get a duplicate copy of the dependency library, and this can create problems.
+Bower does a good job of deduplicating dependencies, but npm does not. If you aren't doing anything (fancy) with refs, there is a good chance that the problem is not with your refs, but rather an issue with having multiple copies of React loaded into your project. Sometimes, when you pull in a third-party module via npm, you will get a duplicate copy of the dependency library, and this can create problems.
 
 If you are using npm... `npm ls` or `npm ls react` might help illuminate.