Adjust list numbering format

Author: wolf99

CONTRIBUTING.md

@@ -15,22 +15,22 @@ Please note that this project is released with a [Contributor Code of Conduct][c
 
 1. Open an [issue][issue] to discuss the change you want to see.
 This helps us coordinate and reduce duplication.
-2. Once we've had some discussion, you're ready to code!
+1. Once we've had some discussion, you're ready to code!
 
 ## Submitting a pull request
 
 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:
+1. Configure and install the dependencies: `dotnet restore`
+1. Make sure the tests pass on your machine: `dotnet test`
+1. Create a new branch: `git switch -c my-branch-name`
+1. Make your change, add tests, and make sure the tests still pass
+1. 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`
-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.
+1. Push to your fork and [submit a pull request][pr]
+1. 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

@@ -106,7 +106,7 @@ run the following:
    If `curl` is not installed, please use your distribution's package manager
    to install it.
 
-2. To download and run the script:
+1. 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 &&

docs/enterprise-config.md

@@ -4,12 +4,12 @@ Git Credential Manager (GCM) can be configured using multiple
 different mechanisms. In order of preference, those mechanisms are:
 
 1. [Environment variables](environment.md)
-2. [Standard Git configuration files](configuration.md)
+1. [Standard Git configuration files](configuration.md)
    1. Repository/local configuration (`.git/config`)
-   2. User/global configuration (`$HOME/.gitconfig` or `%HOME%\.gitconfig`)
-   3. Installation/system configuration (`etc/gitconfig`)
-3. Enterprise system administrator defaults
-4. Compiled default values
+   1. User/global configuration (`$HOME/.gitconfig` or `%HOME%\.gitconfig`)
+   1. Installation/system configuration (`etc/gitconfig`)
+1. Enterprise system administrator defaults
+1. Compiled default values
 
 This model largely matches what Git itself supports, namely environment
 variables that take precedence over Git configuration files.

docs/github-apideprecation.md

@@ -67,9 +67,9 @@ There is a workaround which should work and doesn't require installing anything.
 1. Tell your system administrator they should start planning to upgrade the
    installed version of Git for Windows to at least 2.29! 😁
 
-2. [Create a new personal access token](https://github.com/settings/tokens/new?scopes=repo,gist,workflow) (see official [documentation](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token))
+1. [Create a new personal access token](https://github.com/settings/tokens/new?scopes=repo,gist,workflow) (see official [documentation](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token))
 
-3. Enter a name ("note") for the token and ensure the `repo`, `gist`, and
+1. Enter a name ("note") for the token and ensure the `repo`, `gist`, and
    `workflow` scopes are selected:
    ![image](https://user-images.githubusercontent.com/5658207/95448332-1beb2000-095b-11eb-9a48-9c05b1926a6b.png)
    ...
@@ -79,16 +79,16 @@ There is a workaround which should work and doesn't require installing anything.
    ...
    ![image](https://user-images.githubusercontent.com/5658207/95447343-7b483080-0959-11eb-8e00-151d53893f3f.png)
 
-4. Click "Generate Token"
+1. Click "Generate Token"
 
    ![image](https://user-images.githubusercontent.com/5658207/95448393-31f8e080-095b-11eb-9568-cfd1c567a65c.png)
 
-5. **[IMPORTANT]** Keep the resulting page open as this contains your new token
+1. **[IMPORTANT]** Keep the resulting page open as this contains your new token
    (this will only be displayed once!)
 
    ![image](https://user-images.githubusercontent.com/5658207/95448288-ff4ee800-095a-11eb-9709-8e37bde8b716.png)
 
-6. Save the generated PAT in the Windows Credential Manager:
+1. Save the generated PAT in the Windows Credential Manager:
 
    1. If you prefer to use the command-line, open a command prompt (cmd.exe) and
       type the following:

docs/gitlab.md

@@ -7,11 +7,11 @@ Git Credential Manager supports [gitlab.com](https://gitlab.com) out the box.
 To use on another instance, eg. `https://gitlab.example.com` requires setup and configuration:
 
 1. [Create an OAuth application](https://docs.gitlab.com/ee/integration/oauth_provider.html). This can be at the user, group or instance level. Specify a name and use a redirect URI of `http://127.0.0.1/`. _Unselect_ the 'Confidential' option, and ensure the 'Expire access tokens' option is selected. Set the scope to 'write_repository'.
-2. Copy the application ID and configure `git config --global credential.https://gitlab.example.com.GitLabDevClientId <APPLICATION_ID>`
-3. Copy the application secret and configure `git config --global credential.https://gitlab.example.com.GitLabDevClientSecret <APPLICATION_SECRET>`
-4. Configure authentication modes to include 'browser' `git config --global credential.https://gitlab.example.com.gitLabAuthModes browser`
-5. For good measure, configure `git config --global credential.https://gitlab.example.com.provider gitlab`. This may be necessary to recognise the domain as a GitLab instance.
-6. Verify the config is as expected `git config --global --get-urlmatch credential https://gitlab.example.com`
+1. Copy the application ID and configure `git config --global credential.https://gitlab.example.com.GitLabDevClientId <APPLICATION_ID>`
+1. Copy the application secret and configure `git config --global credential.https://gitlab.example.com.GitLabDevClientSecret <APPLICATION_SECRET>`
+1. Configure authentication modes to include 'browser' `git config --global credential.https://gitlab.example.com.gitLabAuthModes browser`
+1. For good measure, configure `git config --global credential.https://gitlab.example.com.provider gitlab`. This may be necessary to recognise the domain as a GitLab instance.
+1. Verify the config is as expected `git config --global --get-urlmatch credential https://gitlab.example.com`
 
 ### Clearing config
 
@@ -42,5 +42,5 @@ git config --global credential.gitlabauthmodes browser
 Improved support requires changes in GitLab. Please vote for these issues if they affect you:
 
 1. No support for OAuth device authorization (necessary for machines without web browser): [GitLab issue 332682](https://gitlab.com/gitlab-org/gitlab/-/issues/332682)
-2. Only domains with prefix `gitlab.` are recognised as GitLab remotes: [GitLab issue 349464](https://gitlab.com/gitlab-org/gitlab/-/issues/349464)
-3. Username/password authentication is suggested even if disabled on server: [GitLab issue 349463](https://gitlab.com/gitlab-org/gitlab/-/issues/349463)
+1. Only domains with prefix `gitlab.` are recognised as GitLab remotes: [GitLab issue 349464](https://gitlab.com/gitlab-org/gitlab/-/issues/349464)
+1. Username/password authentication is suggested even if disabled on server: [GitLab issue 349463](https://gitlab.com/gitlab-org/gitlab/-/issues/349463)

docs/netconfig.md

@@ -49,11 +49,11 @@ GCM supports other ways of configuring a proxy for convenience and compatibility
 1. GCM-specific configuration options (_**only** respected by GCM; **deprecated**_):
    - `credential.httpProxy`
    - `credential.httpsProxy`
-2. cURL environment variables (_also respected by Git_):
+1. cURL environment variables (_also respected by Git_):
    - `http_proxy`
    - `https_proxy`/`HTTPS_PROXY`
    - `all_proxy`/`ALL_PROXY`
-3. `GCM_HTTP_PROXY` environment variable (_**only** respected by GCM; **deprecated**_)
+1. `GCM_HTTP_PROXY` environment variable (_**only** respected by GCM; **deprecated**_)
 
 Note that with the cURL environment variables there are both lowercase and
 uppercase variants.