changes per cyclus#427, make things consistent

Author: abachma2

source/user/tutorial/add_deploy.rst

@@ -2,8 +2,8 @@ Deploying New Facilities
 ==========================
 
 Often in fuel cycle analysis, transition scenarios are considered. These ask 
-questins like: "How does the 
-commissioning and decommissioning of reactors affect electrity production or 
+questions like: "How does the 
+commissioning and decommissioning of reactors affect electricity production or 
 material transactions?". Transition analysis will
 require an institution that can deploy additional facilities at given time 
 steps: the ``cycamore DeployInst`` archetype.  This is the simplest institution 
@@ -12,7 +12,8 @@ new facilities, in which the user simply defines the times at which new agents
 should be deployed as copies of available prototypes.
 
 In this case, we will keep the current institutions and add another
-institution that will deploy more facilities over time.
+institution that will deploy more facilities over time, which can be used 
+to meet a growing electricity demand in a simulation.
 
 Example: DeployInst
 --------------------------------
@@ -66,27 +67,27 @@ We will now use this to add the institution for ``DeployInst``.
 
 where:
 
-* prototype: Ordered list of prototypes to build
+* prototypes: Ordered list of prototypes to build
 * build_times: Time step on which to deploy agents given in prototype list
 * n_build: Number of each prototype given in prototype list to build
 
 Activity: Add a New Institution 
-++++++++++++++++++++++++++++++++++++++++++
+--------------------------------
 
 Using the table below and the DeployInst template above, fill out the commodities
 template.
 
-+-------------+-------------+---------------------+
++-----------------------+-------------+-----------+
 | Prototype             | build_times | n_build   |
-+=============+=============+=====================+
++=======================+=============+===========+
 | UraniumMine           | 1           | 1         |
-+-------------+-------------+---------------------+
++-----------------------+-------------+-----------+
 | FuelFab               | 1           | 1         |
-+-------------+-------------+---------------------+
++-----------------------+-------------+-----------+
 | 1178MWe BRAIDWOOD_1   | 2           | 1         |
-+-------------+-------------+---------------------+
++-----------------------+-------------+-----------+
 | 1000MWe LIGHTWATER_1  | 3           | 1         |
-+-------------+-------------+---------------------+
++-----------------------+-------------+-----------+
 
 Using the prototype facilities already created, the new institution should
 look like the following:
@@ -121,16 +122,16 @@ look like the following:
       </config>
     </institution>
 
-The above institution will create 1 ``UraniumMine`` and 1 ``FuelFab`` facility on
+The above institution will deploy 1 ``UraniumMine`` and 1 ``FuelFab`` facility on
 time step 1. The next time step will deploy the ``1178MWe BRAIDWOOD_1`` reactor
 prototype. And finally, at time step 3, the ``1000We LIGHTWATER_1`` will be deployed.
 This institution block goes inside the Region block, with the previously created 
-insitutions blocks. 
+institution blocks. 
 
-**ExampleInstitution** is a placeholder for your institution name, and in this scenario
+``ExampleInstitution`` is a placeholder for your institution name, and in this scenario
 only one of each prototype will be deployed since ``n_build`` has a value of 1 for each.
 
 This example is now complete. Save your file as the desired file name (with ``.xml`` 
 extension) and run your code through |Cyclus|. If your simulation runs into errors, 
 sample files can be found `here <https://doi.org/10.5281/zenodo.4557613>`_ under 
-``input_deployinst.xml`` or ``ouput_deployinst.sqlite``.
+``input_deployinst.xml`` or ``output_deployinst.sqlite``.