(DOCSP-11397): Add 'Considerations' to Tasks page (#47)

* (DOCSP-11397): Add 'Considerations' to Tasks page

* Apply suggestions from code review

Co-authored-by: Anthony Sansone <[email protected]>

* copy review

Co-authored-by: Anthony Sansone <[email protected]>

Author: melissamahoney-mongodb

source/style-guide/style/tasks.txt

@@ -3,9 +3,9 @@
 =====
 Tasks
 =====
+.. default-domain:: mongodb
 
-.. include:: /style-guide/includes/page-needs-update.rst
-
+.. include:: /includes/styles/corrections.rst
 A *task* is an action that users perform to achieve a goal, such as
 creating a server. A task topic, article, or section provides the
 action steps and the necessary context and reference information that
@@ -29,12 +29,11 @@ makes more sense or is necessary for clarity.
 
 .. example::
 
-   - Create users in SQL Server
-   - Configure SQL Server Management Studio to connect to SQL Server on
-     Windows
-   - Add new ServiceNet routes to a server
+   - Restart a Running Deployment
+   - Install Ops Manager from Archive on Linux
+   - Add Existing MongoDB Processes to Ops Manager
 
-For guidelines about capitalizing titles, see
+To learn how to capitalize titles, see
 :ref:`titles-and-headings`.
 
 Task Page Structure
@@ -58,10 +57,24 @@ especially if it will take a long time.
     informational topic or in a topic that introduces the task as part
     of a larger process or user goal.
 
+Considerations
+~~~~~~~~~~~~~~
+
+If the task has items that the user should acknowledge or contemplate
+before taking action, describe them in a "Considerations" section that
+precedes any prerequisites or the procedure. You could include the
+following information:
+
+- Descriptions of variations, options, or scopes
+- Hyperlinks to information that prepares the user for any choices they
+  must make
+- Impacts on other areas of the product or later tasks they might want 
+  to complete
+
 Prerequisites
 ~~~~~~~~~~~~~
 
-If the task has requirements that the user *must* meet before taking
+If the task has requirements that the user *must* meet *before* taking
 action, describe them in a "Prerequisites" section that precedes the
 steps. You could include the following information:
 
@@ -84,7 +97,7 @@ Procedures
 A task contains one or more *procedures*, or set of sequential action
 steps. Consider the following guidelines when creating a procedure:
 
--  If the procedure has more than one step, use a numbered list for the
+-  If the procedure has more than one step, use a ``steps`` file for the
    steps. Don't use bullets, except to list choices within a step.
 -  If the procedure has only one step, show that step in a regular
    paragraph. That is, don't number it.