Put visibility info closer to decision info

Author: felicitymay

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

@@ -25,8 +25,6 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 
 {% data reusables.pages.new-or-existing-repo %}
 
-{% data reusables.pages.private_pages_are_public_warning %}
-
 {% data reusables.repositories.create_new %}
 {% data reusables.repositories.owner-drop-down %}
 {% data reusables.pages.create-repo-name %}
@@ -36,6 +34,8 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 
 {% data reusables.pages.must-have-repo-first %}
 
+{% data reusables.pages.private_pages_are_public_warning %}
+
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
   ```shell

content/github/working-with-github-pages/creating-a-github-pages-site.md

@@ -20,8 +20,6 @@ versions:
 
 {% data reusables.pages.new-or-existing-repo %}
 
-{% data reusables.pages.private_pages_are_public_warning %}
-
 {% data reusables.repositories.create_new %}
 {% data reusables.repositories.owner-drop-down %}
 {% data reusables.pages.create-repo-name %}
@@ -33,6 +31,8 @@ versions:
 
 {% data reusables.pages.must-have-repo-first %}
 
+{% data reusables.pages.private_pages_are_public_warning %}
+
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
 3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.

data/reusables/pages/new-or-existing-repo.md

@@ -1,3 +1,6 @@
-If your site is an independent project, you can create a new repository to store your site's source code. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project.
+If your site is an independent project, you can create a new repository to store your site's source code. In this case, it is best to create a public repository. {% data variables.product.prodname_pages %} is supported for private repositories for paid accounts, but using a public repository makes it easy to remember that the content is published publicly.
+
+If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project.
 
 If you want to create a site in an existing repository, skip to the "[Creating your site](#creating-your-site)" section.
+