Per #2282, switching from italics to bold in the update_dtc_website i…

…nstructions. This is very subjective an can easily be backed out if the PR reviewers don't like the change.
dtcenter · Aug 2, 2023 · 2c9bd26 · 2c9bd26
1 parent 03ce222
commit 2c9bd26
Show file tree

Hide file tree

Showing 2 changed files with 31 additions and 31 deletions.
diff --git a/docs/Release_Guide/release_steps/common/update_dtc_website.rst b/docs/Release_Guide/release_steps/common/update_dtc_website.rst
@@ -6,24 +6,24 @@ Update DTC Website
 * Navigate to the downloads page for the |projectRepo| repository at
   https://dtcenter.org/community-code/metplus/download
 
-* Click on the *Edit* button to edit the Downloads page.
+* Click on the **Edit** button to edit the Downloads page.
 
-* Create a new *Software Release* for the newly released version by clicking
-  on *Add New Release*.
+* Create a new **Software Release** for the newly released version by clicking
+  on **Add New Release**.
 
-  * For *Full Title of Release* type "|projectRepo| Version X.Y.Z".
+  * For **Full Title of Release** type "|projectRepo| Version X.Y.Z".
 
-  * For *Related Community Code* select both the "METplus" and the "|projectName|"
+  * For **Related Community Code** select both the "METplus" and the "|projectName|"
     options (For Macs, hold the Command key to select both).
 
-  * For *Version Label* type "|projectRepo| X.Y.Z-betaN".
+  * For **Version Label** type "|projectRepo| X.Y.Z-betaN".
 
-  * Select the *Release Type* ("Recommended" for official or bugfix releases or
+  * Select the **Release Type** ("Recommended" for official or bugfix releases or
     "Development" for development versions).
 
-  * Enter the *Release Date*.
+  * Enter the **Release Date**.
 
-  * Click on *Add Code Download* then click *Add Link* to add links for each of the following:
+  * Click on **Add Code Download** then click **Add Link** to add links for each of the following:
 
     * Add Link: |addTarfileStep|
 
@@ -41,19 +41,19 @@ Update DTC Website
       (If creating a new official release, be sure to add a new *Existing Builds
       and Docker* page, if one was not already created.)
 
-  * Inside the text box in the "Release Notes" section provide a direct link to
-    the *release-notes.html* file in the User's Guide.
+  * In the **Release Notes** text box provide a direct link to the
+    *release-notes.html* file in the User's Guide.
 
-  * Click on "Create Release".
+  * Click on **Create Release**.
 
   * Update the existing releases, as needed.
 
     * For a development release, ensure the "Release Type" is set to
-      *Development* and change any previous *Development* versions to
-      *Other*.
+      **Development** and change any previous **Development** versions to
+      **Other**.
 
     * For a bugfix or official release, change any previous
-      *Recommended* versions to *Other*.
+      **Recommended** versions to **Other**.
 
     * For an official release, remove the corresponding development
       releases.

diff --git a/docs/Release_Guide/release_steps/coordinated/update_dtc_website.rst b/docs/Release_Guide/release_steps/coordinated/update_dtc_website.rst
@@ -6,24 +6,24 @@ Update DTC Website
 * Navigate to the METplus downloads page at
   https://dtcenter.org/community-code/metplus/download
 
-* Click on the *Edit* button to edit the Downloads page.
+* Click on the **Edit** button to edit the Downloads page.
 
-* Create a new *Software Release* for the new coordinated release by clicking
-  on *Add New Release*.
+* Create a new **Software Release** for the new coordinated release by clicking
+  on **Add New Release**.
 
-  * For *Full Title of Release* type "Coorindated METplus X.Y".
+  * For **Full Title of Release** type "Coorindated METplus X.Y".
 
-  * For *Related Community Code* select only the "METplus" option.
+  * For **Related Community Code** select only the "METplus" option.
 
-  * For *Version Label* type "Coordinated METplus X.Y".
+  * For **Version Label** type "Coordinated METplus X.Y".
 
-  * Select the *Release Type* as "Recommended".
+  * Select the **Release Type** as "Recommended".
 
-  * Select the *Release Options* as "Coordinated".
+  * Select the **Release Options** as "Coordinated".
 
-  * Enter the *Release Date*.
+  * Enter the **Release Date**.
 
-  * Click on *Add Code Download* then click *Add Link* to add links for each of the following:
+  * Click on **Add Code Download** then click **Add Link** to add links for each of the following:
 
     * Add Link: Link text should be "METplus X.Y.Z" and the URL should be a link to the METplus component DTC release page.
 
@@ -49,18 +49,18 @@ Update DTC Website
       should be the latest Existing Builds page, i.e.
       https://dtcenter.org/community-code/metplus/metplus-X-Y-existing-builds
 
-  * For the *Release Notes* text box provide direct links to the *release-notes.html*
+  * In the **Release Notes** text box provide direct links to the *release-notes.html*
     files on the main_vX.Y branch of the User's Guide for each component.
 
-  * Click on *Create Release*.
+  * Click on **Create Release**.
 
-  * Update any existing coordinated releases by changing the *Release Type* from
-    "Recommended" to "Other" and click the *Update Release* button.
+  * Update any existing coordinated releases by changing the **Release Type** from
+    "Recommended" to "Other" and click the **Update Release** button.
 
   * Review the existing component releases and remove any remaining development
     releases (e.g. beta and rc) for any of the official releases included in this
     coordinated release.
 
-  * Click on *Save* at the bottom of the page.
+  * Click on **Save** at the bottom of the page.
 
-* Create a new *Existing Builds and Docker* page for the next coordinated release.
+* Create a new **Existing Builds and Docker** page for the next coordinated release.