Part 3: Third fourth content unordered lists from dash to asterisk (#…

…51097)

content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md

@@ -78,9 +78,9 @@ An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through you
 
 There are a couple of reasons your site might be automatically disabled.
 
-- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan)."
-- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository)."
+* If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan)."
+* If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository)."
 
 ## Further reading
 
-- "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"
+* "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"

content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md

@@ -49,8 +49,8 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
 {% data reusables.pages.sidebar-pages %}
 1. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file directly to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow, no `CNAME` file is created, so you need to create one manually (containing only a line of text with your custom domain). For more information about your publishing source, see "[AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
 1. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. If you're implementing IPv6 support, we highly recommend using an `A` record in addition to your `AAAA` record, due to slow adoption of IPv6 globally. {% data reusables.pages.contact-dns-provider %}
-    - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
-    - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    * To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
+    * To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
 
       ```shell
       185.199.108.153
@@ -59,7 +59,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
       185.199.111.153
       ```
 
-    - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    * To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
 
       ```shell
       2606:50c0:8000::153
@@ -71,7 +71,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
 {% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 1. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
-   - For `A` records:
+   * For `A` records:
 
      ```shell
      $ dig EXAMPLE.COM +noall +answer -t A
@@ -81,7 +81,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
      > EXAMPLE.COM    3600    IN A     185.199.111.153
      ```
 
-   - For `AAAA` records:
+   * For `AAAA` records:
 
      ```shell
      $ dig EXAMPLE.COM +noall +answer -t AAAA
@@ -181,4 +181,4 @@ If you get an error about a custom domain being taken, you may need to remove th
 
 ## Further reading
 
-- "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"
+* "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"

content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md

@@ -26,28 +26,28 @@ For your site to render at the correct domain, make sure your CNAME file still e
 
 Then, make sure the CNAME file is formatted correctly.
 
-- The CNAME filename must be all uppercase.
-- The CNAME file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
-- The CNAME file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
-- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's CNAME file contains `example.com`, you cannot use `example.com` in the CNAME file for your repository.
+* The CNAME filename must be all uppercase.
+* The CNAME file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
+* The CNAME file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
+* The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's CNAME file contains `example.com`, you cannot use `example.com` in the CNAME file for your repository.
 
 ## DNS misconfiguration
 
 If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.
 
 You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly:
 
-- A CLI tool such as `dig`. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)".
-- An online DNS lookup tool.
+* A CLI tool such as `dig`. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)".
+* An online DNS lookup tool.
 
 ## Custom domain names that are unsupported
 
 If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.
 
 Make sure your site does not:
-- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
-- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
-- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
+* Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
+* Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
+* Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
 
   The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)."
 

content/pages/getting-started-with-github-pages/about-github-pages.md

@@ -80,9 +80,9 @@ For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/
 
 If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited.
 
-- {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations.
-- {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
-- You cannot create an organization site (a site published from a repository named `<organization>.github.io`)
+* {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations.
+* {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
+* You cannot create an organization site (a site published from a repository named `<organization>.github.io`)
 
 For more information about {% data variables.product.prodname_emus %}, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
 {% endif %}
@@ -117,13 +117,13 @@ Using {% data variables.product.prodname_pages %} to create a copy of an existin
 
 {% data variables.product.prodname_pages %} sites are subject to the following usage limits:
 
-- {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations)"{% endif %}
-- Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
-- {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes.
+* {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations)"{% endif %}
+* Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
+* {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes.
 {% ifversion fpt or ghec %}
-- {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month.
-- {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow.
-- In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body.
+* {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month.
+* {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow.
+* In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body.
 
 If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.github_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs.
 
@@ -144,5 +144,5 @@ When a {% data variables.product.prodname_pages %} site is visited, the visitor'
 
 ## Further reading
 
-- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %}
-- "[AUTOTITLE](/rest/repos#pages)"
+* [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %}
+* "[AUTOTITLE](/rest/repos#pages)"

content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md

@@ -25,8 +25,8 @@ Access control is available for project sites that are published from a private
 
 Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published:
 
-- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
-- We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
+* We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
+* We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
 
 You can see your site's unique subdomain in the "Pages" tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
 

content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md

@@ -35,4 +35,4 @@ shortTitle: Create custom 404 page
 
 ## Further reading
 
-- [Front matter](https://jekyllrb.com/docs/frontmatter) in the Jekyll documentation
+* [Front matter](https://jekyllrb.com/docs/frontmatter) in the Jekyll documentation

content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md

@@ -64,7 +64,7 @@ To customize your site even more, you can use Jekyll, a static site generator wi
 
 ## Further reading
 
-- "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
-- "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)"
-- "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)"
-- "[AUTOTITLE](/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites)"
+* "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+* "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)"
+* "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)"
+* "[AUTOTITLE](/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites)"

content/pages/getting-started-with-github-pages/deleting-a-github-pages-site.md

@@ -15,8 +15,8 @@ shortTitle: Delete a GitHub Pages site
 ## Deleting your site
 
 You can delete your site in two ways:
-- Delete the repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository)."
-- Change the source to the `None` branch. For more information, see [Deleting your site by changing the source](#deleting-your-site-by-changing-the-source) below.
+* Delete the repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository)."
+* Change the source to the `None` branch. For more information, see [Deleting your site by changing the source](#deleting-your-site-by-changing-the-source) below.
 
 If you want to remove the current deployment of your site but do not want to delete the site, you can unpublish your site. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
 

content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md

@@ -51,10 +51,10 @@ If you enable HTTPS for your {% data variables.product.prodname_pages %} site bu
 To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML.
 
 Assets are commonly found in the following locations:
-- If your site uses Jekyll, your HTML files will probably be found in the __layouts_ folder.
-- CSS is usually found in the `<head>` section of your HTML file.
-- JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
-- Images are often found in the `<body>` section.
+* If your site uses Jekyll, your HTML files will probably be found in the __layouts_ folder.
+* CSS is usually found in the `<head>` section of your HTML file.
+* JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
+* Images are often found in the `<body>` section.
 
 {% tip %}