Render site

docs/getting_started.html

@@ -815,28 +815,34 @@ <h4>Making edits to this file if you are not part of the jhudsl GitHub
 <code>sync.yml</code> file you’ll need to - fork the repo - make the
 changes (described below) to <code>sync.yml</code>, committing them to a
 branch - create a PR in the original OTTR repo using your branch</p>
-<p>Detailed instructions for these steps are provided below: - Click the
-pencil in the upper right for “Fork this repository and edit the file” -
-Click the green button that says “Fork this repository” - Make the edits
-to the file, adding your repository’s name where it says
-<code>#NEW REPO HERE#</code>. Be careful to indent the same amount as
-the other repositories listed. <img
-src="https://raw.githubusercontent.com/jhudsl/OTTR_Template/main/resources/screenshots/edit-sync.yml.png" />
-- Click the green “Commit changes…” button. As the banner on the top of
-the page says, this will write your changes to a new branch in your fork
-so you can open a pull request. - Add a commit message or extended
-description beyond what’s there if you want to provide more info and
-click the green Propose Changes button. - This will automatically open a
-new page comparing the changes from your branch to the original repo.
-Click the green “Create pull request” button to create a PR with your
-edits to the sync.yml file to the OTTR repo. - Edit the title or provide
-an extended description beyond what’s there if you want (if you already
-did that when you created your commit, GitHub will copy that over).
-Click the green “Create pull request” button. This will create a PR in
-the OTTR repo. - To make sure that we see the PR, you’ll want to add a
-comment with <code>@cansavvy</code> to alert us there’s a PR that needs
-to be merged. Scroll down to “Add a comment”, type the
-<code>@cansavvy</code>, and click the green “Comment” button.</p>
+<p>Detailed instructions for these steps are provided below:</p>
+<ul>
+<li>Click the pencil in the upper right for “Fork this repository and
+edit the file”</li>
+<li>Click the green button that says “Fork this repository”</li>
+<li>Make the edits to the file, adding your repository’s name where it
+says <code>#NEW REPO HERE#</code>. Be careful to indent the same amount
+as the other repositories listed. <img
+src="https://raw.githubusercontent.com/jhudsl/OTTR_Template/main/resources/screenshots/edit-sync.yml.png" /></li>
+<li>Click the green “Commit changes…” button. As the banner on the top
+of the page says, this will write your changes to a new branch in your
+fork so you can open a pull request.</li>
+<li>Add a commit message or extended description beyond what’s there if
+you want to provide more info and click the green Propose Changes
+button.</li>
+<li>This will automatically open a new page comparing the changes from
+your branch to the original repo. Click the green “Create pull request”
+button to create a PR with your edits to the sync.yml file to the OTTR
+repo.</li>
+<li>Edit the title or provide an extended description beyond what’s
+there if you want (if you already did that when you created your commit,
+GitHub will copy that over). Click the green “Create pull request”
+button. This will create a PR in the OTTR repo.</li>
+<li>To make sure that we see the PR, you’ll want to add a comment with
+<code>@cansavvy</code> to alert us there’s a PR that needs to be merged.
+Scroll down to “Add a comment”, type the <code>@cansavvy</code>, and
+click the green “Comment” button.</li>
+</ul>
 <p>Some alternative information on these steps are available <a
 href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork">here
 from GitHub</a> or from <a