Add release notes for native core; update links.

docs/comparisons/hubs/README.md

@@ -25,4 +25,4 @@ Hubs allows for a maximum of 24 users to be present in the same space due to per
 
 Hubs uses the [MPL 2.0](https://github.com/mozilla/hubs/blob/master/LICENSE) license, which is a good benefit to project security as it helps ensure that your organization can maintain its copy of the code even if the maintainer stops supporting it. However, this license specifically requires changes to the code to be made open source, thus causing some friction for organizations who want to maintain a competitive advantage or maintain code-security through obfuscation.
 
-Vircadia however uses the [Apache 2.0](https://github.com/vircadia/vircadia/blob/master/LICENSE) open source license which allows the same privileges with the added benefit of being able to keep all code changes closed source if desired. This allows organizations to maintain a competitive advantage or heightened code-security.
+Vircadia however uses the [Apache 2.0](https://github.com/vircadia/vircadia-native-core/blob/master/LICENSE) open source license which allows the same privileges with the added benefit of being able to keep all code changes closed source if desired. This allows organizations to maintain a competitive advantage or heightened code-security.

docs/comparisons/omniverse/README.md

@@ -23,8 +23,8 @@ Both platforms encourage real-time collaborative creation of worlds. However, Om
 
 Nvidia Omniverse is a premium toolkit for designing and developing components for 3D products. It is however closed source and requires continued licensing for many of its features. Also, due to its proprietary nature, if Nvidia decides to stop developing Omniverse, the cost and burden of migrating to a new development pipeline is borne by the user.
 
-Vircadia however uses the [Apache 2.0](https://github.com/vircadia/vircadia/blob/master/LICENSE) open source license which is a good benefit to project security as it helps ensure that your organization can maintain its copy of the code even if the maintainer stops supporting it. It also has the added benefit of being able to keep all code changes closed source if desired. This allows organizations to maintain a competitive advantage or heightened code-security.
+Vircadia however uses the [Apache 2.0](https://github.com/vircadia/vircadia-native-core/blob/master/LICENSE) open source license which is a good benefit to project security as it helps ensure that your organization can maintain its copy of the code even if the maintainer stops supporting it. It also has the added benefit of being able to keep all code changes closed source if desired. This allows organizations to maintain a competitive advantage or heightened code-security.
 
 ## Deployment
 
-Omniverse is designed as a collaborative development platform first and foremost, where mass-user distribution is meant to be handled in separate steps. Vircadia differs in the way that it encourages collaborative editing and production deployment of UX friendly worlds, enabling an end-to-end workflow in a completely free and open source environment.
+Omniverse is designed as a collaborative development platform first and foremost, where mass-user distribution is meant to be handled in separate steps. Vircadia differs in the way that it encourages collaborative editing and production deployment of UX friendly worlds, enabling an end-to-end workflow in a completely free and open source environment.

docs/domain-server/README.md

@@ -5,7 +5,7 @@ slug: /domain-server
 
 # Overview
 
-The Vircadia Domain server (codename Athena) is developed in this [repository](https://github.com/vircadia/vircadia) and uses the following stack:
+The Vircadia Domain server (codename Athena) is developed in this [repository](https://github.com/vircadia/vircadia-native-core) and uses the following stack:
 
 1. HTML & JavaScript - Web based control panel
 1. [Qt](https://qt.io/) - C++ framework
@@ -36,16 +36,16 @@ The Vircadia Domain server (codename Athena) is developed in this [repository](h
 
 ## Compiling from Source
 
-You can find general build information [here](https://github.com/vircadia/vircadia/blob/master/BUILD.md#general-build-information).
+You can find general build information [here](https://github.com/vircadia/vircadia-native-core/blob/master/BUILD.md#general-build-information).
 
 Specific build information for each platform:
-* [Windows](https://github.com/vircadia/vircadia/blob/master/BUILD_WIN.md#build-windows)
-* [Linux](https://github.com/vircadia/vircadia/blob/master/BUILD_LINUX.md#build-linux)
-* [MacOS](https://github.com/vircadia/vircadia/blob/master/BUILD_OSX.md#build-osx)
+* [Windows](https://github.com/vircadia/vircadia-native-core/blob/master/BUILD_WIN.md#build-windows)
+* [Linux](https://github.com/vircadia/vircadia-native-core/blob/master/BUILD_LINUX.md#build-linux)
+* [MacOS](https://github.com/vircadia/vircadia-native-core/blob/master/BUILD_OSX.md#build-osx)
 
 ## Packaging
 
-All packaging specific information and steps for the Vircadia Domain server can be found [here](https://github.com/vircadia/vircadia/blob/master/INSTALLER.md#creating-an-installer).
+All packaging specific information and steps for the Vircadia Domain server can be found [here](https://github.com/vircadia/vircadia-native-core/blob/master/INSTALLER.md#creating-an-installer).
 
 ## Configuration