You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-14Lines changed: 18 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
ms.date: 9/15/2023
2
+
ms.date: 05/16/2025
3
3
---
4
4
5
5
# Overview
@@ -23,44 +23,48 @@ Contributors who make infrequent or small updates can edit the file directly on
23
23
2. On learn.microsoft.com, find the article that you want to update.
24
24
3. Above the title of the article, select **Edit this document**.
25
25
26
-
26
+
27
27
28
-
4. The corresponding article file opens on GitHub. Select **Edit this file**.
28
+
4. The corresponding article file opens on GitHub. Select **Edit**.
29
29
30
-
30
+
31
31
32
-
5. The article file opens in a line-numbered editor page where you can make updates.
32
+
5. If a **You need to fork this repository to propose changes** page opens, select **Fork this repository**.
33
+
34
+
35
+
36
+
6. The article file opens in a line-numbered editor page where you can make updates.
33
37
34
38
Articles on learn.microsoft.com are formatted using the Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/).
35
39
36
40
> [!TIP]
37
-
> Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
41
+
> Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName>`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
38
42
39
43
Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates.
40
44
41
45
When you're finished making changes, select the green **Commit changes** button.
42
46
43
-
47
+
44
48
45
-
6. In the **Propose changes** dialog that opens, review and/or enter the following values:
49
+
7. In the **Propose changes** dialog that opens, review and/or enter the following values:
46
50
-**Commit message**: This value is required. You can accept the default value ("Update \<filename\>") or you can change it.
47
51
-**Extended description**: This value is optional. For example:
48
52
- An explanation of the changes.
49
53
- @ include the GitHub alias of someone to review and merge your changes.
50
54
51
55
When you're finished on the **Propose changes** dialog, select the green **Propose changes** button.
52
56
53
-
57
+
54
58
55
-
7. On the **Comparing changes** page that opens, select the green **Create pull request** button.
59
+
8. On the **Comparing changes** page that opens, select the green **Create pull request** button.
56
60
57
-
61
+
58
62
59
-
8. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
63
+
9. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
60
64
61
-
65
+
62
66
63
-
9. That's it. There's nothing more for you to do.
67
+
10. That's it. There's nothing more for you to do.
64
68
65
69
The article owner (identified in metadata) is notified about the changes to the article. Eventually, the article owner or another party will review, possibly edit, and approve your changes. After your pull request is merged, the article is updated on learn.microsoft.com.
0 commit comments