Fix md lint errors that do not alter content

Author: wolf99

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-## Contributing
+# Contributing
 
-[issue]: https://github.com/GitCredentialManager/git-credential-manager/issues 
+[issue]: https://github.com/GitCredentialManager/git-credential-manager/issues
 [fork]: https://github.com/GitCredentialManager/git-credential-manager/fork
 [pr]: https://github.com/GitCredentialManager/git-credential-manager/compare
 [code-of-conduct]: CODE_OF_CONDUCT.md
@@ -13,24 +13,24 @@ Please note that this project is released with a [Contributor Code of Conduct][c
 
 ## Start with an issue
 
-0. Open an [issue][issue] to discuss the change you want to see.
+1. Open an [issue][issue] to discuss the change you want to see.
 This helps us coordinate and reduce duplication.
-0. Once we've had some discussion, you're ready to code!
+2. Once we've had some discussion, you're ready to code!
 
 ## Submitting a pull request
 
-0. [Fork][fork] and clone the repository
-0. Configure and install the dependencies: `dotnet restore`
-0. Make sure the tests pass on your machine: `dotnet test`
-0. Create a new branch: `git switch -c my-branch-name`
-0. Make your change, add tests, and make sure the tests still pass
-0. For UI updates, test your changes by executing a `dotnet run` in applicable UI-related project directories:
+1. [Fork][fork] and clone the repository
+2. Configure and install the dependencies: `dotnet restore`
+3. Make sure the tests pass on your machine: `dotnet test`
+4. Create a new branch: `git switch -c my-branch-name`
+5. Make your change, add tests, and make sure the tests still pass
+6. For UI updates, test your changes by executing a `dotnet run` in applicable UI-related project directories:
     - `Atlassian.Bitbucket.UI.Avalonia`
     - `GitHub.UI.Avalonia`
     - `Atlassian.Bitbucket.UI.Windows`
     - `GitHub.UI.Windows`
-0. Push to your fork and [submit a pull request][pr]
-0. Pat your self on the back and wait for your pull request to be reviewed and merged.
+7. Push to your fork and [submit a pull request][pr]
+8. Pat your self on the back and wait for your pull request to be reviewed and merged.
 
 Here are a few things you can do that will increase the likelihood of your pull request being accepted:
 

README.md

@@ -97,24 +97,24 @@ run the following:
 
 1. To ensure `curl` is installed:
 
-```shell
-curl --version
-```
+   ```shell
+   curl --version
+   ```
 
-If `curl` is not installed, please use your distribution's package manager
-to install it.
+   If `curl` is not installed, please use your distribution's package manager
+   to install it.
 
-0. To download and run the script:
+2. To download and run the script:
 
-```shell
-curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh &&
-sh ./install-from-source.sh &&
-git-credential-manager-core configure
-```
+   ```shell
+   curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh &&
+   sh ./install-from-source.sh &&
+   git-credential-manager-core configure
+   ```
 
-__Note:__ You will be prompted to enter your credentials so that the script
-can download GCM's dependencies using your distribution's package
-manager.
+   **Note:** You will be prompted to enter your credentials so that the script
+   can download GCM's dependencies using your distribution's package
+   manager.
 
 #### Ubuntu/Debian distributions
 
@@ -124,7 +124,8 @@ Download the latest [.deb package](https://github.com/GitCredentialManager/git-c
 sudo dpkg -i <path-to-package>
 git-credential-manager-core configure
 ```
-__Note:__ Although packages were previously offered on certain
+
+**Note:** Although packages were previously offered on certain
 [Microsoft Ubuntu package feeds](https://packages.microsoft.com/repos/),
 GCM no longer publishes to these repositories. Please install the
 Debian package using the above instructions instead.
@@ -249,7 +250,7 @@ See detailed information [here](https://aka.ms/gcm/httpproxy).
 
 ## Contributing
 
-This project welcomes contributions and suggestions.  
+This project welcomes contributions and suggestions.
 See the [contributing guide](CONTRIBUTING.md) to get started.
 
 This project follows [GitHub's Open Source Code of Conduct](CODE_OF_CONDUCT.md).

SECURITY.md

@@ -1,3 +1,5 @@
+# Security
+
 If you discover a security issue in this repo, please submit it through the [GitHub Security Bug Bounty](https://hackerone.com/github)
 
 Thanks for helping make GitHub products safe for everyone.

docs/bitbucket-development.md

@@ -65,18 +65,18 @@ The Access and Refresh Tokens will be stored against the username and the userna
 
 # On-Premise Bitbucket
 
-On-premise Bitbucket, more correctly known as Bitbucket Server or Bitbucket DC, has a number of differences compared to the cloud instance of Bitbucket, https://bitbucket.org. 
+On-premise Bitbucket, more correctly known as Bitbucket Server or Bitbucket DC, has a number of differences compared to the cloud instance of Bitbucket, https://bitbucket.org.
 
 As far as GCMC is concerned the main difference it doesn't support OAuth so only Basic Authentication is available.
 
 It is possible to test with Bitbucket Server by running it locally using the following command from the Atlassian SDK:
 
-	❯ atlas-run-standalone --product bitbucket
+    ❯ atlas-run-standalone --product bitbucket
 
 See https://developer.atlassian.com/server/framework/atlassian-sdk/atlas-run-standalone/.
 
 This will download and run a standalone instance of Bitbucket Server which can be accessed using the credentials `admin`/`admin` at
 
-	https://localhost:7990/bitbucket
+    https://localhost:7990/bitbucket
 
 Instructions on how to download and install the Atlassian SDK can be found here: https://developer.atlassian.com/server/framework/atlassian-sdk/

docs/configuration.md

@@ -196,7 +196,6 @@ git config --global credential.httpsProxy http://john.doe:[email protected]
 Override the available authentication modes presented during Bitbucket authentication.
 If this option is not set, then the available authentication modes will be automatically detected.
 
-
 **Note:** This setting only applies to Bitbucket.org, and not Server or DC instances.
 
 **Note:** This setting supports multiple values separated by commas.
@@ -227,7 +226,6 @@ Enabling this option will improve performance when using Oauth2 and interacting
 
 Enabling this option will decrease performance when using Basic Auth by requiring the user the re-enter credentials everytime.
 
-
 Value|Refresh Credentials Before Returning
 -|-
 `true`, `1`, `yes`, `on` |Always
@@ -295,7 +293,6 @@ git config --global credential.gitLabAuthModes "browser"
 
 ---
 
-
 ### credential.namespace
 
 Use a custom namespace prefix for credentials read and written in the OS credential store.
@@ -332,7 +329,7 @@ _(unset)_|Windows: `wincredman`<br/>macOS: `keychain`<br/>Linux: _(none)_|-
 `cache`|Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache).|Windows, macOS, Linux
 `plaintext`|Store credentials in plaintext files (**UNSECURE**). Customize the plaintext store location with [`credential.plaintextStorePath`](#credentialplaintextstorepath).|Windows, macOS, Linux
 
-##### Example
+#### Example
 
 ```bash
 git config --global credential.credentialStore gpg
@@ -475,6 +472,7 @@ Credential: "git:https://github.com" (user = alice)
    https://github.com/contoso/widgets
    https://[email protected]/contoso/widgets
 ```
+
 ```text
 Credential: "git:https://[email protected]" (user = bob)
 
@@ -489,17 +487,20 @@ Credential: "git:https://github.com/foo/bar" (user = alice)
 
    https://github.com/foo/bar
 ```
+
 ```text
 Credential: "git:https://github.com/contoso/widgets" (user = alice)
 
    https://github.com/contoso/widgets
    https://[email protected]/contoso/widgets
 ```
+
 ```text
 Credential: "git:https://[email protected]/foo/bar" (user = bob)
 
    https://[email protected]/foo/bar
 ```
+
 ```text
 Credential: "git:https://[email protected]/example/myrepo" (user = bob)
 

docs/development.md

@@ -106,7 +106,7 @@ $ dotnet test --collect:"XPlat Code Coverage" --settings=./.code-coverage/coverl
 
 Or via the VSCode Terminal/Run Task:
 
-```
+```console
 test with coverage
 ```
 
@@ -115,6 +115,7 @@ HTML reports can be generated using ReportGenerator, this should be installed du
 ```shell
 $ dotnet ~/.nuget/packages/reportgenerator/*/*/net6.0/ReportGenerator.dll -reports:./**/TestResults/**/coverage.cobertura.xml -targetdir:./out/code-coverage
 ```
+
 or
 
 ```shell
@@ -123,12 +124,12 @@ $ dotnet {$env:USERPROFILE}/.nuget/packages/reportgenerator/*/*/net6.0/ReportGen
 
 Or via VSCode Terminal/Run Task:
 
-```
+```console
 report coverage - nix
 ```
 
 or
 
-```
+```console
 report coverage - win
-```
+```

docs/enterprise-config.md

@@ -18,7 +18,7 @@ The addition of the enterprise system administrator defaults enables those
 administrators to configure many GCM settings using familiar MDM tooling, rather
 than having to modify the Git installation configuration files.
 
-### User Freedom
+## User Freedom
 
 We believe the user should _always_ be at liberty to configure
 Git and GCM exactly as they wish. By prefering environment variables and Git
@@ -30,13 +30,13 @@ that can always be overriden by the user in the usual ways.
 Default setting values come from the Windows Registry, specifically the
 following keys:
 
-**32-bit Windows**
+### 32-bit Windows
 
 ```text
 HKEY_LOCAL_MACHINE\SOFTWARE\GitCredentialManager\Configuration
 ```
 
-**64-bit Windows**
+### 64-bit Windows
 
 ```text
 HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GitCredentialManager\Configuration
@@ -55,7 +55,6 @@ those of the [Git configuration](configuration.md) settings.
 The type of each registry key can be either `REG_SZ` (string) or `REG_DWORD`
 (integer).
 
-
 ## macOS/Linux
 
 Default configuration setting stores has not been implemented.