Merge pull request #163 from richy58729/master

Jaykul · web-flow · commit e8f4250996dc · 2023-05-04T20:30:36.000-07:00
A few suggestions for improvement
diff --git a/Best-Practices/Language-Interop-and-.NET.md b/Best-Practices/Language-Interop-and-.NET.md
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 ## Contributing
 
-Are you interested in helping create the style guide, or do you just want to change a specific rule? You may use the issues system or Github pull requests freely to suggests corrections and simple changes to rules. However, if you want to add a completely new rule, or totally change a rule, please open an issue and let us discuss it!
+Are you interested in helping create the style guide, or do you just want to change a specific rule? You may use the issues system or Github pull requests freely to suggest corrections and simple changes to rules. However, if you want to add a completely new rule, or totally change a rule, please open an issue and let us discuss it!
 
 ### Tone
 
diff --git a/LICENSE.md b/LICENSE.md
@@ -13,7 +13,7 @@ The authors encourage you to redistribute this content as widely as possible, bu
 
 #### Credits
 
-_The Community Book of PowerShell Practices_ was originally compiled and edited by Don Jones and Matt Penny with input from the Windows PowerShell community on PowerShell.org
+_The Community Book of PowerShell Practices_ was originally compiled and edited by Don Jones and Matt Penny with input from the Windows PowerShell community on PowerShell.org.
 
 Portions copyright (c) Don Jones, Matt Penny, 2014-2015
 
@@ -27,7 +27,7 @@ Portions copyright (c) Joel Bennett, 2015
 
 #### NOTE
 
-The *PowerShell Best Practices* are always evolving, and continue to be edited and updated as the language and tools (and our community understanding of them) evolve. We encourage you to check back for new editions at least twice a year, by visiting [https://github.com/PoshCode/PowerShellPracticeAndStyle](https://github.com/PoshCode/PowerShellPracticeAndStyle)
+The *PowerShell Best Practices* are always evolving, and continue to be edited and updated as the language and tools (and our community understanding of them) evolve. We encourage you to check back for new editions at least twice a year, by visiting [https://github.com/PoshCode/PowerShellPracticeAndStyle](https://github.com/PoshCode/PowerShellPracticeAndStyle).
 
 The *PowerShell Style Guide* in particular is in PREVIEW, and we are still actively working out our disagreements about the rules in the guide through the GitHub issues system. Please don't be surprised if over then next few weeks we change rules to contradict what they say at this current moment.
 
diff --git a/README.md b/README.md
@@ -43,26 +43,26 @@ The guidelines are divided into these sections:
   * [Error Handling](Best-Practices/Error-Handling.md)
   * [Performance](Best-Practices/Performance.md)
   * [Security](Best-Practices/Security.md)
-  * [Language, Interop and .Net](Best-Practices/Language-Interop-and-.Net.md)
+  * [Language, Interop and .NET](Best-Practices/Language-Interop-and-.NET.md)
   * [Metadata, Versioning, and Packaging](Best-Practices/Metadata-Versioning-and-Packaging.md)
 
 ### Current State:
 
-Remember [what we mean by _Best Practices_](#what-are-best-practices)
+Remember [what we mean by _Best Practices_](#what-are-best-practices).
 
-The *PowerShell Best Practices* are always evolving, and continue to be edited and updated as the language and tools (and our community understanding of them) evolve. We encourage you to check back for new editions at least twice a year, by visiting [https://github.com/PoshCode/PowerShellPracticeAndStyle](https://github.com/PoshCode/PowerShellPracticeAndStyle)
+The *PowerShell Best Practices* are always evolving, and continue to be edited and updated as the language and tools (and our community understanding of them) evolve. We encourage you to check back for new editions at least twice a year, by visiting [https://github.com/PoshCode/PowerShellPracticeAndStyle](https://github.com/PoshCode/PowerShellPracticeAndStyle).
 
 The *PowerShell Style Guide* in particular is in PREVIEW, and we are still actively working out our disagreements about the rules in the guide through the GitHub issues system.
 
 #### Contributing
 
 Please use the issues system or GitHub pull requests to make corrections, contributions, and other changes to the text - we welcome your contributions!
 
-For more information, see [CONTRIBUTING](CONTRIBUTING.md)
+For more information, see [CONTRIBUTING](CONTRIBUTING.md).
 
 #### Credits
 
-_The Community Book of PowerShell Practices_ was originally compiled and edited by Don Jones and Matt Penny with input from the Windows PowerShell community on PowerShell.org
+_The Community Book of PowerShell Practices_ was originally compiled and edited by Don Jones and Matt Penny with input from the Windows PowerShell community on PowerShell.org.
 
 Portions copyright (c) Don Jones, Matt Penny, 2014-2015
 
diff --git a/TableOfContents.md b/TableOfContents.md
@@ -23,5 +23,5 @@ PowerShell Practice and Style Guide
 * [Error Handling](Best-Practices/Error-Handling.md)
 * [Performance](Best-Practices/Performance.md)
 * [Security](Best-Practices/Security.md)
-* [Language, Interop and .Net](Best-Practices/Language-Interop-and-.Net.md)
+* [Language, Interop and .NET](Best-Practices/Language-Interop-and-.NET.md)
 * [Metadata, Versioning, and Packaging](Best-Practices/Metadata-Versioning-and-Packaging.md)
