Yet more wording refinements.

Signed-off-by: Dean Wampler <dean.wampler@ibm.com>

Author: deanwampler

README.md

@@ -21,7 +21,7 @@ Next Steps after running the script:
 1. Go to [https://github.com/The-AI-Alliance](https://github.com/The-AI-Alliance) and create a _public_ repo named with the same name you used. If you don't have permissions, ask Dean Wampler, Adam Pingel, Joe Olson, or Trevor Grant to do this.
 3. Follow the instructions given for adding a remote (upstream) location to your local repo. If someone else creates the repo for you, remind them to give you the instructions!
 4. Push your local content up to the remote repo! TIP: Make sure both the `main` and `latest` branches are pushed upstream.
-5. In GitHub, go to the repo Settings, "Pages" section (left-hand side) to set up GitHub Pages publishing. You want to select `docs` as the folder from which the site is published and `latest` as the branch.
+5. In GitHub, go to the repo Settings, "Pages" section (left-hand side) to set up GitHub Pages publishing. You want to select `docs` as the folder from which the site is published and `latest` as the branch. (There are more detail instructions in the `README.md` generated for your site, if needed.)
 
 A simpler experience is just to use `main` as the publication branch, so every merge to `main` automatically publishes your updated content. If you really want to do this, ask Dean Wampler for help.
 

create-microsite.sh

@@ -234,6 +234,29 @@ Done! The current working directory is $PWD.
 
 Next Steps:
 
+1. Go to https://github.com/The-AI-Alliance and create a _public_ repo named with the same name you used. 
+   If you don't have permissions, ask Dean Wampler, Adam Pingel, Joe Olson, or Trevor Grant to do this.
+3. Follow the instructions given for adding a remote (upstream) location to your local repo. 
+   If someone else creates the repo for you, remind them to give you the instructions!
+4. Push your local content up to the remote repo! TIP: Make sure both the "main" and "latest" branches are
+   pushed upstream.
+5. In GitHub, go to the repo Settings, "Pages" section (left-hand side) to set up GitHub Pages publishing.
+   You want to select "docs" as the folder from which the site is published and "latest" as the branch.
+   (There are more detail instructions in the "README.md" generated for your site, if needed.)
+
+A simpler experience is just to use "main" as the publication branch, so every merge to "main" 
+automatically publishes your updated content. If you really want to do this, ask Dean Wampler for help.
+
+Next, replace the placeholder text and "*.markdown" files with your real content, e.g.,
+
+1. Replace all occurrences of "TODO" with appropriate content.
+2. Rename or delete the "second_page.markdown". Copy it to add more top-level pages, but change the 
+   "nav_order" field!
+3. Use the "nested" directory content as an example of nesting content or delete it if you don't need it.
+4. Make any changes you want to make in the "docs/_config.yml" file. (None are required.)
+
+See also the "README.md" that was created in your new repo for more tips and guidance on development tasks. 
+
 1. Go to https://github.com/The-AI-Alliance and create a repo named "$repo_name". 
    If you don't have permissions, as Dean Wampler, Adam Pingel, Joe Olson, or Trevor Grant to do this.
 2. Follow the instructions given for adding a remote (upstream) location to your local repo.