s/dblock/oshi/g (oshi#880)

Author: dblock

CONTRIBUTING.md

@@ -1,16 +1,16 @@
 Contributing to Oshi
 =====================
 
-Oshi is work of [many contributors](https://github.com/dblock/oshi/graphs/contributors). You're encouraged to submit [pull requests](https://github.com/dblock/oshi/pulls), [propose features and discuss issues](https://github.com/dblock/oshi/issues).
+Oshi is work of [many contributors](https://github.com/oshi/oshi/graphs/contributors). You're encouraged to submit [pull requests](https://github.com/oshi/oshi/pulls), [propose features and discuss issues](https://github.com/oshi/oshi/issues).
 
 #### Fork the Project
 
-Fork the [project on Github](https://github.com/dblock/oshi) and check out your copy.
+Fork the [project on Github](https://github.com/oshi/oshi) and check out your copy.
 
 ```
 git clone https://github.com/contributor/oshi.git
 cd oshi
-git remote add upstream https://github.com/dblock/oshi.git
+git remote add upstream https://github.com/oshi/oshi.git
 ```
 
 #### Create a Topic Branch
@@ -92,7 +92,7 @@ git push origin my-feature-branch -f
 Update the [CHANGELOG](CHANGELOG.md) with the pull request number. A typical entry looks as follows.
 
 ```
-* [#123](https://github.com/dblock/oshi/pull/123): Reticulated splines - [@contributor](https://github.com/contributor).
+* [#123](https://github.com/oshi/oshi/pull/123): Reticulated splines - [@contributor](https://github.com/contributor).
 ```
 
 Amend your previous commit and force push the changes.

FAQ.md

@@ -1,6 +1,6 @@
 What is the intended use of the API?
 ========
-Users should create a new instance of [SystemInfo](http://dblock.github.io/oshi/apidocs/oshi/SystemInfo.html). This provides access to the platform-specific hardware and software interfaces using the respective `get*()` methods. The interfaces in `oshi.hardware` and `oshi.software.os` provide cross-platform functionality. See the `main()` method of [SystemInfoTest](https://github.com/dblock/oshi/blob/master/oshi-core/src/test/java/oshi/SystemInfoTest.java) for sample code.
+Users should create a new instance of [SystemInfo](http://dblock.github.io/oshi/apidocs/oshi/SystemInfo.html). This provides access to the platform-specific hardware and software interfaces using the respective `get*()` methods. The interfaces in `oshi.hardware` and `oshi.software.os` provide cross-platform functionality. See the `main()` method of [SystemInfoTest](https://github.com/oshi/oshi/blob/master/oshi-core/src/test/java/oshi/SystemInfoTest.java) for sample code.
 
 Methods return a "snapshot" of current levels. To display values which change over time, it is intended that users poll for information no more frequently than one second. Disk and file system calls may incur some latency and should be polled less frequently. OSHI 4.X will overhaul this behavior; see the [UPGRADING.md](UPGRADING.md) document for more details.
 

RELEASING.md

@@ -12,8 +12,8 @@ Releasing OSHI
 
 ### Prepare
 
-* Make sure tests are green on [Travis CI](https://travis-ci.org/dblock/oshi).
-* Review [SonarQube](https://sonarqube.com/overview?id=com.github.dblock%3Aoshi-parent) for any bugs.
+* Make sure tests are green on [Travis CI](https://travis-ci.org/oshi/oshi).
+* Review [SonarQube](https://sonarcloud.io/dashboard?id=com.github.oshi%3Aoshi-parent) for any bugs.
 * Run `mvn clean test` on every OS you have access to
 * Choose an appropriate [version number](http://semver.org/) for the release
  	* Proactively change version numbers in the download links on [README.md](README.md).
@@ -38,10 +38,10 @@ Releasing OSHI
 * `mvn release:perform`
 	* Takes a few minutes. 
 	* This pushes the release to the [Nexus](https://oss.sonatype.org/) staging repository
-	* This also pushes to [gh_pages](https://dblock.github.io/oshi)
+	* This also pushes to [gh_pages](https://oshi.github.io/oshi)
 * Log on to [Nexus](https://oss.sonatype.org/) and [release the deployment from OSSRH to the Central Repository](http://central.sonatype.org/pages/releasing-the-deployment.html).
 
-* Add a title and release notes [to the tag](https://github.com/dblock/oshi/tags) on GitHub and publish the release to make it current.
+* Add a title and release notes [to the tag](https://github.com/oshi/oshi/tags) on GitHub and publish the release to make it current.
 
 * As development progresses, update version in [pom.xml](pom.xml) using -SNAPSHOT appended to the new version using [Semantic Versioning](http://semver.org/) standards:
 	* Increment major version (x.0) for API-breaking changes or additions