Updated Microsoft to MicrosoftDocs

Author: alfredmyers

CONTRIBUTING.md

@@ -19,7 +19,7 @@ The content inside the **docs** folder is organized into sections that are organ
 
 You can skip this first step for small changes.
 
-**Step 2:** Fork the `Microsoft/visualstudio-docs` repo.
+**Step 2:** Fork the `MicrosoftDocs/visualstudio-docs` repo.
 
 **Step 3:** Create a `branch` for your article.
 
@@ -42,7 +42,7 @@ Be sure to follow the proper Markdown syntax. See the [style guide](./styleguide
           /media
               debugging-installed-app-package.png
 
-**Step 5:** Submit a Pull Request (PR) from your branch to `Microsoft/visualstudio-docs/master`.
+**Step 5:** Submit a Pull Request (PR) from your branch to `MicrosoftDocs/visualstudio-docs/master`.
 
 If your PR is addressing an existing issue, add the `Fixes #Issue_Number` keyword to the commit message or PR description, so the issue can be automatically closed when the PR is merged. For more information, see [Closing issues via commit messages](https://help.github.com/articles/closing-issues-via-commit-messages/).