deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fixing broken image

Browse Source
This commit is contained in:
LizRoss 2017-04-07 14:43:44 -07:00
parent 99c5f81ee3
commit 210e90524c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.md
View File

@ -20,7 +20,7 @@ We've tried to make editing an existing, public file as simple as possible.
1. Go to the page on TechNet that you want to update, and then click **Contribute**. 1. Go to the page on TechNet that you want to update, and then click **Contribute**.
![GitHub Web, showing the Contribute link](images/contribute-link.png) ![GitHub Web, showing the Contribute link](images/contribute-link.png)
2. Log into (or sign up for) a GitHub account. 2. Log into (or sign up for) a GitHub account.
@ -28,7 +28,7 @@ We've tried to make editing an existing, public file as simple as possible.
3. Click the **Pencil** icon (in the red box) to edit the content. 3. Click the **Pencil** icon (in the red box) to edit the content.
![GitHub Web, showing the Pencil icon in the red box](images/pencil-icon.png) ![GitHub Web, showing the Pencil icon in the red box](images/pencil-icon.png)
4. Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see: 4. Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see:
- **If you're linked to the Microsoft organization in GitHub:** [Windows Open Publishing Guide Home](http://aka.ms/windows-op-guide) - **If you're linked to the Microsoft organization in GitHub:** [Windows Open Publishing Guide Home](http://aka.ms/windows-op-guide)
@ -37,7 +37,7 @@ We've tried to make editing an existing, public file as simple as possible.
5. Make your suggested change, and then click **Preview Changes** to make sure it looks correct. 5. Make your suggested change, and then click **Preview Changes** to make sure it looks correct.
![GitHub Web, showing the Preview Changes tab](images/preview-changes.png) ![GitHub Web, showing the Preview Changes tab](images/preview-changes.png)
6. When you’re done editing the topic, scroll to the bottom of the page, and then click **Propose file change** to create a fork in your personal GitHub account. 6. When you’re done editing the topic, scroll to the bottom of the page, and then click **Propose file change** to create a fork in your personal GitHub account.
@ -48,7 +48,7 @@ We've tried to make editing an existing, public file as simple as possible.
7. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in. 7. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in.
If there are no problems, you’ll see the message, **Able to merge**. If there are no problems, you’ll see the message, **Able to merge**.
![GitHub Web, showing the Comparing changes screen](images/compare-changes.png) ![GitHub Web, showing the Comparing changes screen](images/compare-changes.png)
8. Click **Create pull request**. 8. Click **Create pull request**.