Update docs for new org

docs/development/atom-shell-vs-node-webkit.md

@@ -47,4 +47,4 @@ By using the [multi-context](http://strongloop.com/strongblog/whats-new-node-js-
 feature of Node, Electron doesn't introduce a new JavaScript context in web
 pages.
 
-[node-bindings]: https://github.com/atom/electron/tree/master/atom/common
+[node-bindings]: https://github.com/electron/electron/tree/master/atom/common

docs/development/build-instructions-linux.md

@@ -41,7 +41,7 @@ device container of at least 25 gigabytes in size.
 ## Getting the Code
 
 ```bash
-$ git clone https://github.com/atom/electron.git
+$ git clone https://github.com/electron/electron.git
 ```
 
 ## Bootstrapping

docs/development/build-instructions-osx.md

@@ -16,7 +16,7 @@ following python modules:
 ## Getting the Code
 
 ```bash
-$ git clone https://github.com/atom/electron.git
+$ git clone https://github.com/electron/electron.git
 ```
 
 ## Bootstrapping

docs/development/build-instructions-windows.md

@@ -27,7 +27,7 @@ building with Visual Studio will come in the future.
 ## Getting the Code
 
 ```powershell
-$ git clone https://github.com/atom/electron.git
+$ git clone https://github.com/electron/electron.git
 ```
 
 ## Bootstrapping
@@ -84,7 +84,7 @@ $ python script\test.py
 ```
 
 Tests that include native modules (e.g. `runas`) can't be executed with the
-debug build (see [#2558](https://github.com/atom/electron/issues/2558) for
+debug build (see [#2558](https://github.com/electron/electron/issues/2558) for
 details), but they will work with the release build.
 
 To run the tests with the release build use:

docs/development/coding-style.md

@@ -44,4 +44,4 @@ etc.
 When creating a new API, we should prefer getters and setters instead of
 jQuery's one-function style. For example, `.getText()` and `.setText(text)`
 are preferred to `.text([text])`. There is a
-[discussion](https://github.com/atom/electron/issues/46) on this.
+[discussion](https://github.com/electron/electron/issues/46) on this.