Repo sync

content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md

@@ -227,10 +227,12 @@ When you first publish a package, the default visibility is private and only you
 {% data reusables.package_registry.package-settings-option %}
 1. At the bottom of the page, under "Danger Zone", click **Change visibility** and choose a visibility setting:
     - To make the package visible to anyone, click **Public**.
-     {% warning %}
 
-     **Warning:** Once you make a package public, you cannot make it private again.
+      {% warning %}
+
+      **Warning:** Once you make a package public, you cannot make it private again.
+
+      {% endwarning %}
 
-     {% endwarning %}
     - To make the package visible to a custom selection of people in your organization, click **Private**.{% ifversion not fpt %}
     - To make the package visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.{% endif %}

content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md

@@ -147,31 +147,31 @@ You can use gems from {% data variables.product.prodname_registry %} much like y
 {% data reusables.package_registry.authenticate-step %}
 1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your _Gemfile_ to fetch gems from this new source. For example, you can add a new `source` block to your _Gemfile_ that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing `GEM_NAME` with the package you want to install from {% data variables.product.prodname_registry %} and `NAMESPACE` with the personal account or organization {% ifversion packages-rubygems-v2 %}to which the gem you want to install is scoped{% else %}that owns the repository containing the gem you want to install{% endif %}.{% ifversion ghes %} Replace `REGISTRY_URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace `HOSTNAME` with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY_URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace `HOSTNAME` with the hostname of {% data variables.location.product_location %}.{% endif %}
 
-  ```ruby
-  source "https://rubygems.org"
+   ```ruby
+   source "https://rubygems.org"
 
-  gem "rails"
+   gem "rails"
 
-  source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY_URL{% endif %}/NAMESPACE" do
-    gem "GEM_NAME"
-  end
-  ```
+   source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY_URL{% endif %}/NAMESPACE" do
+     gem "GEM_NAME"
+   end
+   ```
 
 1. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](https://bundler.io/gemfile.html).
 
-  ```ruby
-  source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY_URL{% endif %}/NAMESPACE"
-  source "https://rubygems.org"
+   ```ruby
+   source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY_URL{% endif %}/NAMESPACE"
+   source "https://rubygems.org"
 
-  gem "rails"
-  gem "GEM_NAME"
-  ```
+   gem "rails"
+   gem "GEM_NAME"
+   ```
 
 1. Install the package:
 
-  ```shell
-  gem install GEM_NAME --version "0.1.1"
-  ```
+   ```shell
+   gem install GEM_NAME --version "0.1.1"
+   ```
 
 ## Further reading
 

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

@@ -47,27 +47,27 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 {% 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 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. For more information about your publishing source, see "[AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
 
-  {% note %}
+   {% note %}
 
-  **Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
+   **Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
 
-  For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
+   For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
 
-  {% endnote %}
+   {% endnote %}
 
 1. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `another.example.com` for your organization site, create a `CNAME` record that points `another.example.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
 {% 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 _WWW.EXAMPLE.COM_ with your subdomain.
 
-```shell
-    $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
-    > ;WWW.EXAMPLE.COM.                    IN      A
-    > WWW.EXAMPLE.COM.             3592    IN      CNAME   YOUR-USERNAME.github.io.
-    > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER .
-    > GITHUB-PAGES-SERVER .         22      IN      A       192.0.2.1
-```
+   ```shell
+   $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+   > ;WWW.EXAMPLE.COM.                    IN      A
+   > WWW.EXAMPLE.COM.             3592    IN      CNAME   YOUR-USERNAME.github.io.
+   > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER .
+   > GITHUB-PAGES-SERVER .         22      IN      A       192.0.2.1
+   ```
 
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
@@ -103,21 +103,21 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
 {% 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:
-    ```shell
-    $ dig EXAMPLE.COM +noall +answer -t A
-    > EXAMPLE.COM    3600    IN A     185.199.108.153
-    > EXAMPLE.COM    3600    IN A     185.199.109.153
-    > EXAMPLE.COM    3600    IN A     185.199.110.153
-    > EXAMPLE.COM    3600    IN A     185.199.111.153
-    ```
+     ```shell
+     $ dig EXAMPLE.COM +noall +answer -t A
+     > EXAMPLE.COM    3600    IN A     185.199.108.153
+     > EXAMPLE.COM    3600    IN A     185.199.109.153
+     > EXAMPLE.COM    3600    IN A     185.199.110.153
+     > EXAMPLE.COM    3600    IN A     185.199.111.153
+     ```
    - For `AAAA` records:
-    ```shell
-    $ dig EXAMPLE.COM +noall +answer -t AAAA
-    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8000::153
-    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8001::153
-    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8002::153
-    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8003::153
-    ```
+     ```shell
+     $ dig EXAMPLE.COM +noall +answer -t AAAA
+     > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8000::153
+     > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8001::153
+     > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8002::153
+     > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8003::153
+     ```
 
       Remember to also check your `A` record.
 {% data reusables.pages.build-locally-download-cname %}
@@ -134,13 +134,13 @@ After you configure the apex domain, you must configure a CNAME record with your
 1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 1. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
 
-```shell
-    $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
-    > ;WWW.EXAMPLE.COM                     IN      A
-    > WWW.EXAMPLE.COM.              3592    IN      CNAME   YOUR-USERNAME.github.io.
-    > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER.
-    > GITHUB-PAGES-SERVER.         22      IN      A       192.0.2.1
-```
+   ```shell
+   $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+   > ;WWW.EXAMPLE.COM                     IN      A
+   > WWW.EXAMPLE.COM.              3592    IN      CNAME   YOUR-USERNAME.github.io.
+   > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER.
+   > GITHUB-PAGES-SERVER.         22      IN      A       192.0.2.1
+   ```
 
 ## Removing a custom domain
 

content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md

@@ -68,20 +68,20 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 {% data reusables.pages.navigate-publishing-source %}
   For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder.
 
- ```shell
- $ mkdir docs
- # Creates a new folder called docs
- $ cd docs
- ```
-
- If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
-
- ```shell
- $ git checkout --orphan gh-pages
- # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch
- $ git rm -rf .
- # Removes the contents from your default branch from the working directory
- ```
+    ```shell
+    $ mkdir docs
+    # Creates a new folder called docs
+    $ cd docs
+    ```
+
+    If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+
+    ```shell
+    $ git checkout --orphan gh-pages
+    # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch
+    $ git rm -rf .
+    # Removes the contents from your default branch from the working directory
+    ```
 
 1. To create a new Jekyll site, use the `jekyll new` command:
 

data/reusables/pages/check-workflow-run.md

@@ -1,10 +1,10 @@
 {% ifversion build-pages-with-actions %}
 1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".
 
-  {% note %}
+   {% note %}
 
-  **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration)".
+   **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration)".
 
-  {% endnote %}
+   {% endnote %}
 
 {% endif %}

data/reusables/pages/visit-site.md

@@ -1,8 +1,8 @@
 1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**.
 ![Screenshot of a confirmation message for {% data variables.product.prodname_pages %} listing the site's URL. To the right of the URL, a button labeled "Visit site" is outlined in dark orange.](/assets/images/help/pages/click-pages-url-to-preview.png)
 
-  {% note %}
+   {% note %}
 
-  {% data reusables.pages.twenty-minutes-to-publish %}
+   {% data reusables.pages.twenty-minutes-to-publish %}
 
-  {% endnote %}
+   {% endnote %}