CONTRIBUTING.md in vcloud-edge_gateway-1.0.0 vs CONTRIBUTING.md in vcloud-edge_gateway-1.0.1

@@ -4,11 +4,11 @@
 
 ## A quick guide on how to contribute
 
 1. Clone the repo:
 
-        git clone [e-mail]:alphagov/vcloud-edge_gateway.git
+        git clone [e-mail]:gds-operations/vcloud-edge_gateway.git
 
 2. Run `bundle` to get the required dependecies
 
 3. Run the tests. Pull requests that add features must include unit tests,
    so it is good to ensure you've got them passing to begin with.
@@ -16,19 +16,19 @@
         bundle exec rake
 
    If you have access to a live environment for testing, it would be great
    if you could run the integration tests too - for more details on the
    set-up for that, please see the [integration tests README]
-   (https://github.com/alphagov/vcloud-edge_gateway/blob/master/spec/integration/README.md)
+   (https://github.com/gds-operations/vcloud-edge_gateway/blob/master/spec/integration/README.md)
 
 4. Add your functionality or bug fix and a test for your change. Only refactoring and
    documentation changes do not require tests. If the functionality is at all complicated
    then it is likely that more than one test will be required. If you would like help
    with writing tests please do ask us.
 
 5. Make sure all the tests pass, including the integration tests if possible.
 
-6. Update the [CHANGELOG](https://github.com/alphagov/vcloud-edge_gateway/blob/master/CHANGELOG.md)
+6. Update the [CHANGELOG](https://github.com/gds-operations/vcloud-edge_gateway/blob/master/CHANGELOG.md)
    with a short description of what the change is. This may be a feature, a bugfix, or an
    API change. If your change is documenation or refactoring, you do not need to add a line
    to the CHANGELOG.
 
 7. Fork the repo, push to your fork, and submit a pull request.