Part 2: Second fourth content unordered lists from dash to asterisk (#51095)

content/get-started/getting-started-with-git/about-remote-repositories.md

@@ -22,8 +22,8 @@ A remote URL is Git's fancy way of saying "the place where your code is stored."
 
 You can only push to two types of URL addresses:
 
-- An HTTPS URL like `https://{% data variables.product.product_url %}/user/repo.git`
-- An SSH URL, like `git@{% data variables.product.product_url %}:user/repo.git`
+* An HTTPS URL like `https://{% data variables.product.product_url %}/user/repo.git`
+* An SSH URL, like `git@{% data variables.product.product_url %}:user/repo.git`
 
 Git associates a remote URL with a name, and your default remote is usually called `origin`.
 
@@ -59,8 +59,8 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit
 {% tip %}
 
 **Tips**:
-- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
-- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop)."
+* You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
+* To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop)."
 
 {% endtip %}
 

content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md

@@ -27,8 +27,8 @@ shortTitle: Caching credentials
 
 1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux.
 1. In the command line, enter `gh auth login`, then follow the prompts.
-   - When prompted for your preferred protocol for Git operations, select `HTTPS`.
-   - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`.
+   * When prompted for your preferred protocol for Git operations, select `HTTPS`.
+   * When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`.
 
 For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 

content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md

@@ -69,8 +69,8 @@ The `.gitattributes` file must be created in the root of the repository and comm
 
 A `.gitattributes` file looks like a table with two columns:
 
-- On the left is the file name for Git to match.
-- On the right is the line ending configuration that Git should use for those files.
+* On the left is the file name for Git to match.
+* On the right is the line ending configuration that Git should use for those files.
 
 ### Example
 
@@ -95,13 +95,13 @@ Here's an example `.gitattributes` file. You can use it as a template for your r
 
 You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
 
-- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
+* `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
 
-- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
+* `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
 
-- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
+* `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
 
-- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
+* `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
 
 ## Refreshing a repository after changing line endings
 
@@ -138,7 +138,7 @@ To ensure that all the line endings in your repository match your new configurat
 
 ## Further reading
 
-- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
-- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
-- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
-- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
+* [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
+* [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
+* [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
+* [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)

content/get-started/getting-started-with-git/ignoring-files.md

@@ -56,7 +56,7 @@ Use your favorite text editor to open the file called `.git/info/exclude` within
 
 ## Further Reading
 
-- [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Git documentation
-- [.gitignore](https://git-scm.com/docs/gitignore) in the Git documentation
-- [A collection of useful _.gitignore_ templates](https://github.com/github/gitignore) in the github/gitignore repository
-- [gitignore.io](https://www.gitignore.io/) site
+* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Git documentation
+* [.gitignore](https://git-scm.com/docs/gitignore) in the Git documentation
+* [A collection of useful _.gitignore_ templates](https://github.com/github/gitignore) in the github/gitignore repository
+* [gitignore.io](https://www.gitignore.io/) site

content/get-started/getting-started-with-git/managing-remote-repositories.md

@@ -29,8 +29,8 @@ shortTitle: Manage remote repositories
 To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
 
 The `git remote add` command takes two arguments:
-- A remote name, for example, `origin`
-- A remote URL, for example, `https://{% data variables.product.product_url %}/OWNER/REPOSITORY.git`
+* A remote name, for example, `origin`
+* A remote URL, for example, `https://{% data variables.product.product_url %}/OWNER/REPOSITORY.git`
 
 For example:
 
@@ -56,9 +56,9 @@ $ git remote add origin https://{% data variables.product.product_url %}/octocat
 ```
 
 To fix this, you can:
-- Use a different name for the new remote.
-- Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
-- Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
+* Use a different name for the new remote.
+* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
+* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
 
 ## Changing a remote repository's URL
 
@@ -72,15 +72,15 @@ The `git remote set-url` command changes an existing remote repository URL.
 
 The `git remote set-url` command takes two arguments:
 
-- An existing remote name. For example, `origin` or `upstream` are two common choices.
-- A new URL for the remote. For example:
-  - If you're updating to use HTTPS, your URL might look like:
+* An existing remote name. For example, `origin` or `upstream` are two common choices.
+* A new URL for the remote. For example:
+  * If you're updating to use HTTPS, your URL might look like:
 
   ```shell
   https://{% data variables.product.product_url %}/OWNER/REPOSITORY.git
   ```
 
-  - If you're updating to use SSH, your URL might look like:
+  * If you're updating to use SSH, your URL might look like:
 
   ```shell
   git@{% data variables.product.product_url %}:OWNER/REPOSITORY.git
@@ -160,8 +160,8 @@ Check that you've correctly typed the remote name.
 Use the `git remote rename` command to rename an existing remote.
 
 The `git remote rename` command takes two arguments:
-- An existing remote name, for example, `origin`
-- A new name for the remote, for example, `destination`
+* An existing remote name, for example, `origin`
+* A new name for the remote, for example, `destination`
 
 ### Example of renaming a remote repository
 
@@ -204,7 +204,7 @@ This error means that the remote name you want to use already exists. To solve t
 Use the `git remote rm` command to remove a remote URL from your repository.
 
 The `git remote rm` command takes one argument:
-- A remote name, for example, `destination`
+* A remote name, for example, `destination`
 
 Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
 
@@ -248,4 +248,4 @@ Check that you've correctly typed the remote name.
 
 ## Further reading
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+* ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)

content/get-started/getting-started-with-git/set-up-git.md

@@ -32,9 +32,9 @@ If you want to work with Git locally, but do not want to use the command line, y
 
 If you do not need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:
 
-- [AUTOTITLE](/repositories/creating-and-managing-repositories/quickstart-for-repositories)
-- [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
-- [Managing files](/repositories/working-with-files/managing-files)
+* [AUTOTITLE](/repositories/creating-and-managing-repositories/quickstart-for-repositories)
+* [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
+* [Managing files](/repositories/working-with-files/managing-files)
 
 ## Setting up Git
 
@@ -76,10 +76,10 @@ If you clone with SSH, you must generate SSH keys on each computer you use to pu
 
 You now have Git and {% data variables.product.prodname_dotcom %} all set up. You may now choose to create a repository where you can put your projects. Saving your code in a repository allows you to back up your code and share it around the world.
 
-- {% data reusables.getting-started.create-a-repository %}
+* {% data reusables.getting-started.create-a-repository %}
 
-- {% data reusables.getting-started.fork-a-repository %}
+* {% data reusables.getting-started.fork-a-repository %}
 
-- {% data reusables.getting-started.being-social %}
+* {% data reusables.getting-started.being-social %}
 
-- {% data reusables.support.connect-in-the-forum-bootcamp %}
+* {% data reusables.support.connect-in-the-forum-bootcamp %}

content/get-started/getting-started-with-git/setting-your-username-in-git.md

@@ -56,5 +56,5 @@ Changing the name associated with your Git commits using `git config` will only
 
 ## Further reading
 
-- "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)"
-- ["Git Configuration" from the _Pro Git_ book](https://git-scm.com/book/en/Customizing-Git-Git-Configuration)
+* "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)"
+* ["Git Configuration" from the _Pro Git_ book](https://git-scm.com/book/en/Customizing-Git-Git-Configuration)

content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md

@@ -46,4 +46,4 @@ If it's successful, nothing will print out. To test that it works, try and clone
 
 ## Further reading
 
-- "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)"
+* "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)"

content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md

@@ -20,6 +20,6 @@ You can avoid being prompted for your password by configuring Git to [cache your
 
 ## Further reading
 
-- "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)"
-- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)"
-- "[AUTOTITLE](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"
+* "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)"
+* "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)"
+* "[AUTOTITLE](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"