From b832f0e0af5c23380095d3d29b65fb194c98f694 Mon Sep 17 00:00:00 2001
From: Jeff Borsecnik <36546697+jborsecnik@users.noreply.github.com>
Date: Fri, 16 Dec 2022 10:32:38 -0800
Subject: [PATCH] Update README.md
---
README.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README.md b/README.md
index 76123f3fb56..8220260a52e 100644
--- a/README.md
+++ b/README.md
@@ -12,11 +12,11 @@ Contributors who only make infrequent or small updates can edit the file directl
2. Browse to the page you want to edit on Microsoft Learn.
3. On the right-hand side of the page, click **Edit** (pencil icon).
- 
+ 
4. The corresponding topic file on GitHub opens, where you need to click the **Edit this file** pencil icon.
- 
+ 
5. The topic opens in a line-numbered editing page where you can make changes to the file. Files in GitHub are written and edited using Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/). Select the **Preview changes** tab to view your changes as you go.
@@ -27,15 +27,15 @@ Contributors who only make infrequent or small updates can edit the file directl
When you're ready, click the green **Propose file change** button.
- 
+ 
7. On the **Comparing changes** page that appears, click the green **Create pull request** button.
- 
+ 
8. On the **Open a pull request** page that appears, click the green **Create pull request** button.
- 
+ 
> [!NOTE]
> Your permissions in the repo determine what you see in the last several steps. People with no special privileges will see the **Propose file change** section and subsequent confirmation pages as described. People with permissions to create and approve their own pull requests will see a similar **Commit changes** section with extra options for creating a new branch and fewer confirmation pages.
The point is: click any green buttons that are presented to you until there are no more.