Update non-issues git url (#1)

docs/architecture/server/README.md

@@ -27,7 +27,7 @@ pets](https://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattl
 
 Routerlicious as a whole is a collection of microservices. These microservices are designed to handle a single task and
 have clear input and output characteristics. Many can be run as serverless lambdas and in fact we have our own [lambda
-framework](https://github.com/microsoft/Prague/tree/master/packages/server/lambdas-driver/src/kafka-service). We chose
+framework](https://github.com/Microsoft/FluidFramework/tree/master/packages/server/lambdas-driver/src/kafka-service). We chose
 this path to have greater control over the throughput and latency characteristics of our message processing. But could
 be also be run with Azure Functions, AWS Lambdas, Fission, etc.
 
@@ -72,7 +72,7 @@ across the pool of Paparazzi instances (snapshot, spell check, entity extraction
 Historian is in charge of storing document snapshots. It itself is a cached proxy to an underlying content-addressable
 file system represented via the [Git REST API](https://developer.github.com/v3/git/). Storage providers that implement
 this interface are then able to plug into the system as a whole. Currently we have support for
-[GitHub](https://developer.github.com/v3/git/), [Git](https://github.com/microsoft/Prague/tree/master/server/gitrest),
+[GitHub](https://developer.github.com/v3/git/), [Git](https://github.com/Microsoft/FluidFramework/tree/master/server/gitrest),
 and [Cobalt](https://offnet.visualstudio.com/officenet/_git/cobalt-netcore).
 
 ## Distributed data structures

docs/contributing/README.md

@@ -3,9 +3,9 @@
 There are many ways to contribute to the Fluid project: logging bugs, submitting pull requests with bug fixes or
 new features, reporting issues, and adding to documentation.
 
-Check out the [issues list](https://github.com/Microsoft/Prague/issues) for ways you can contribute. Issues
-labeled [help wanted](https://github.com/Microsoft/Prague/labels/help%20wanted) are good issues to submit a PR
-for. Issues labeled [good first issue](https://github.com/Microsoft/Prague/labels/good%20first%20issue) are great
+Check out the [issues list](https://github.com/Microsoft/FluidFramework/issues) for ways you can contribute. Issues
+labeled [help wanted](https://github.com/Microsoft/FluidFramework/labels/help%20wanted) are good issues to submit a PR
+for. Issues labeled [good first issue](https://github.com/Microsoft/FluidFramework/labels/good%20first%20issue) are great
 candidates to pick up if you are in the code for the first time. If you are contributing significant changes, please
 discuss with the assignee of the issue first before starting to work on the issue.
 

docs/docfx.json

@@ -45,7 +45,7 @@
       "_appTitle": "Fluid Documentation",
       "_enableSearch": true,
       "_gitContribute": {
-        "repo": "https://github.com/Microsoft/Prague",
+        "repo": "https://github.com/Microsoft/FluidFramework",
         "branch": "master"
       }
     },

docs/examples/README.md

@@ -5,15 +5,15 @@ uid: examples
 # Examples
 
 You can find a number of examples in the Fluid repo, under the
-[samples/chaincode](https://github.com/microsoft/Prague/tree/master/samples/chaincode)
+[samples/chaincode](https://github.com/Microsoft/FluidFramework/tree/master/samples/chaincode)
 path. The following is a list of good examples to start with.
 
 Also see <xref:yo-fluid-details>.
 
 
 ## Clicker
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/clicker)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/clicker)
 
 **Complexity:** Simple
 
@@ -29,7 +29,7 @@ Clicker is a simple example to familiarize yourself with Fluid's component scaff
 
 ## Todo
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/todo)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/todo)
 
 **Complexity:** Intermediate
 
@@ -46,19 +46,19 @@ in a different canvas.
 
 ## ProgressBar
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/todo)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/todo)
 
 
 ## ImageGallery
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/image-gallery)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/image-gallery)
 
 
 ## Pond
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/pond)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/pond)
 
 
 ## Pinpoint editor
 
-[Source code](https://github.com/microsoft/Prague/tree/release/0.6/packages/components/pinpoint-editor)
+[Source code](https://github.com/Microsoft/FluidFramework/tree/release/0.6/packages/components/pinpoint-editor)

docs/get-started/README.md

@@ -18,7 +18,7 @@ The quickest way to get started with Fluid is to build a component. Here's what
 
 The Fluid packages are published to our [private NPM feed](xref:package-feed)
 
-The Fluid Framework repo lives at[https://github.com/Microsoft/Prague/](https://github.com/Microsoft/Prague/)
+The Fluid Framework repo lives at[https://github.com/Microsoft/FluidFramework/](https://github.com/Microsoft/FluidFramework/)
 
 # Repo Access
 

docs/get-started/terminology.md

@@ -23,7 +23,7 @@ See [Containers](xref:concepts#containers)
 
 ## Loader
 
-See <https://github.com/Microsoft/Prague/blob/master/samples/hosts/README.md>
+See <https://github.com/Microsoft/FluidFramework/blob/master/samples/hosts/README.md>
 
 ## Quorum
 

docs/get-started/yo-fluid.md

@@ -22,4 +22,4 @@ See <xref:yo-fluid-details>
 
 ## Yo fluid source
 
-See <https://github.com/Microsoft/Prague/blob/master/tools/generator-fluid/>
+See <https://github.com/Microsoft/FluidFramework/blob/master/tools/generator-fluid/>

docs/index.md

@@ -46,7 +46,7 @@ See [this draft document](xref:what-is-fluid) for some more information about Fl
 
 ## Get the Fluid source code, including examples
 
-The repository is located at <https://github.com/Microsoft/Prague/>. To gain access you will need to link your GitHub
+The repository is located at <https://github.com/Microsoft/FluidFramework/>. To gain access you will need to link your GitHub
 and Microsoft accounts. To do so follow the instructions at <https://repos.opensource.microsoft.com/link>.
 
 After linking your accounts you should be added to the <https://github.com/orgs/Microsoft/teams/everyone> group which
@@ -62,6 +62,6 @@ The Fluid team answers **questions** on the [Microsoft Stack Overflow](https://s
 the [Prague](https://stackoverflow.microsoft.com/questions/tagged/prague) and
 [Fluid](https://stackoverflow.microsoft.com/questions/tagged/fluid) tags.
 
-Bugs, suggestions, and issues should be directed to our [issues page](https://github.com/Microsoft/Prague/issues).
+Bugs, suggestions, and issues should be directed to our [issues page](https://github.com/Microsoft/FluidFramework/issues).
 
 Logistical questions can be directed to our [Teams group](https://teams.microsoft.com/l/team/19%3a10ccb94cae324ec2aabcd6b6322b1a25%40thread.skype/conversations?groupId=9ce27575-2f82-4689-abdb-bcff07e8063b&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47).

packages/server/gateway/views/home.hjs

@@ -11,7 +11,7 @@
     <h2>Get The Source Code</h2>
     <p>
         The repository is located at
-        <a href="https://github.com/Microsoft/Prague/">https://github.com/Microsoft/Prague/</a>. To gain
+        <a href="https://github.com/Microsoft/FluidFramework/">https://github.com/Microsoft/FluidFramework/</a>. To gain
         access you will need to link your GitHub and Microsoft accounts. To do so follow the instructions at
         <a href="https://repos.opensource.microsoft.com/link">https://repos.opensource.microsoft.com/link</a>.
     </p>
@@ -71,7 +71,7 @@
         <a href="https://stackoverflow.microsoft.com/questions/tagged/prague">Prague tag.</a>
         <br>
         Bugs, suggestions, and issues should be directed to our
-        <a href="https://github.com/Microsoft/Prague/issues">issues page.</a>
+        <a href="https://github.com/Microsoft/FluidFramework/issues">issues page.</a>
         <br>
         Logistical questions can be directed to our
         <a

packages/server/lambdas/src/foreman/README.md

@@ -17,6 +17,6 @@ export interface IForeman {
 
 ## Agent loader
 
-Foreman also supports runtime module uploading and distribution. We are using minio portal temporarily as our upload portal. Navigate to http://pragueminio.westus2.cloudapp.azure.com:9000/ (or http://localhost:9000 when running locally) and upload a zipped module inside the agents bucket. Instruction to build and prepare a module can be found [here](https://github.com/Microsoft/Prague/tree/master/doc/modules/resume-analytics#module-agent).
+Foreman also supports runtime module uploading and distribution. We are using minio portal temporarily as our upload portal. Navigate to http://pragueminio.westus2.cloudapp.azure.com:9000/ (or http://localhost:9000 when running locally) and upload a zipped module inside the agents bucket. Instruction to build and prepare a module can be found [here](https://github.com/Microsoft/FluidFramework/tree/master/doc/modules/resume-analytics#module-agent).
 
 Foreman passes the module to all connected server (Paparazzi) and client workers. Server worker downloads the module from minio and loads it as a regular npm module. Client worker uses a webpacked version of the same module (also uploaded in minio in <module-name>/index.js format).

packages/server/routerlicious/src/foreman/README.md

@@ -17,6 +17,6 @@ export interface IForeman {
 
 ## Agent loader
 
-Foreman also supports runtime module uploading and distribution. We are using minio portal temporarily as our upload portal. Navigate to http://pragueminio.westus2.cloudapp.azure.com:9000/ (or http://localhost:9000 when running locally) and upload a zipped module inside the agents bucket. Instruction to build and prepare a module can be found [here](https://github.com/Microsoft/Prague/tree/master/doc/modules/resume-analytics#module-agent).
+Foreman also supports runtime module uploading and distribution. We are using minio portal temporarily as our upload portal. Navigate to http://pragueminio.westus2.cloudapp.azure.com:9000/ (or http://localhost:9000 when running locally) and upload a zipped module inside the agents bucket. Instruction to build and prepare a module can be found [here](https://github.com/Microsoft/FluidFramework/tree/master/doc/modules/resume-analytics#module-agent).
 
 Foreman passes the module to all connected server (Paparazzi) and client workers. Server worker downloads the module from minio and loads it as a regular npm module. Client worker uses a webpacked version of the same module (also uploaded in minio in <module-name>/index.js format).

samples/hosts/README.md

@@ -338,7 +338,7 @@ And that's all that's needed to create or load Fluid documents. It's intended to
 setup as a host. And once done you gain full access to the power of the Fluid platform.
 
 Once you have a host setup the next best step to try is using our Fluid generator to create a new component.
-Insructions for that are at https://github.com/Microsoft/Prague/blob/master/tools/generator-fluid/README.md.
+Insructions for that are at https://github.com/Microsoft/FluidFramework/blob/master/tools/generator-fluid/README.md.
 You can then publish this package to Verdaccio and load it inside of your new loader!
 
 When creating your new component also note that the API provides it access to the underlying loader. You can use this