Merge pull request #1053 from OpenMDAO/minor_doc_fixes

Minor spelling fixes

docs/dymos_book/examples/balanced_field/balanced_field.ipynb

@@ -639,7 +639,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Finally, we setup the OpenMDAO problem, set the intial guesses, and execute the problem by both running the driver and simulating the resulting trajectory.,"
+    "Finally, we setup the OpenMDAO problem, set the initial guesses, and execute the problem by both running the driver and simulating the resulting trajectory.,"
    ]
   },
   {
@@ -694,7 +694,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The figure below shows the resulting simuilated trajectory and confirms that range at the end of phase `rto` is equal to `range` at the end of climb.\n",
+    "The figure below shows the resulting simulated trajectory and confirms that range at the end of phase `rto` is equal to `range` at the end of climb.\n",
     "This is the shortest possible field that accommodates both a rejected takeoff and a takeoff after a single engine failure at V1.\n",
     "\n",
     "The following input cell may be expanded to see how we plotted the data."

docs/dymos_book/examples/bryson_denham/bryson_denham.ipynb

@@ -115,7 +115,7 @@
     "    v_f &= -1.0\n",
     "\\end{align}\n",
     "\n",
-    "In addition, $x$ is consrained to remain below a displacement of 1/9.\n",
+    "In addition, $x$ is constrained to remain below a displacement of 1/9.\n",
     "\n",
     "\\begin{align}\n",
     "    x &\\le 1/9\n",
@@ -304,7 +304,7 @@
     "\n",
     "In addition to `time`, we have three states (`x`, `v`, and `J`) and a single control (`u`).  \n",
     "\n",
-    "Here we use bounds on the states themselves to constrain the initial and final value of `x` and1 `v`, and the initial value of `J`.\n",
+    "Here we use bounds on the states themselves to constrain the initial and final value of `x` and `v`, and the initial value of `J`.\n",
     "From an optimization perspective, this means that we are removing the first and last values in the state histories of $x$ and $v$ from the vector of design variables.\n",
     "Their initial and final values will remain unchanged throughout the optimization process.\n",
     "\n",

docs/dymos_book/examples/commercial_aircraft/commercial_aircraft.ipynb

@@ -86,7 +86,7 @@
     "the ODE model, obtaining accurate derivatives is paramount. Computing\n",
     "derivatives with finite differences in the presence of nonlinear solvers\n",
     "can lead to inaccurate derivatives based on the properties of the\n",
-    "solver. With OpenMDAO's unified derivatives framework, the sensitivy to\n",
+    "solver. With OpenMDAO's unified derivatives framework, the sensitivity to\n",
     "solver tolerances is greatly reduced.\n",
     "\n",
     "### Pitfalls of Differential Inclusion\n",
@@ -142,7 +142,7 @@
     "previous solution. In the context of OpenMDAO, even explicit components\n",
     "constitute subsystems. This can lead to poorly converged solutions.\n",
     "\n",
-    "Setting the _solve\\_subystems_ option to True will force\n",
+    "Setting the _solve\\_subsystems_ option to True will force\n",
     "subsystems to be updated, making sure that all derivative information is\n",
     "up-to-date."
    ]

docs/dymos_book/features/phases/timeseries.ipynb

@@ -81,7 +81,7 @@
     "to add multiple outputs to the timeseries simultaneously.  For instance, just passing '*' as the variable\n",
     "name will add all dynamic outputs of the ODE to the timeseries.\n",
     "\n",
-    "Dymos will ignore any ODE oututs that are not sized such that the first dimension is the same as the\n",
+    "Dymos will ignore any ODE outputs that are not sized such that the first dimension is the same as the\n",
     "number of nodes in the ODE.  That is, if the output variable doesn't appear to be dynamic, it will not\n",
     "be included in the timeseries outputs.\n",
     "\n",

dymos/phase/phase.py

@@ -1453,7 +1453,7 @@ def add_timeseries_output(self, name, output_name=None, units=_unspecified, shap
         output_name : str or None or list or dict
             The name of the variable as listed in the phase timeseries outputs. By
             default this is the last element in `name` when split by dots.  The user may
-            override the constraint name if splitting the path causes name collisions.
+            override the timeseries name if splitting the path causes name collisions.
         units : str or None or _unspecified
             The units to express the timeseries output.  If None, use the
             units associated with the target.  If provided, must be compatible with
@@ -1513,7 +1513,7 @@ def add_timeseries_rate_output(self, name, output_name=None, units=_unspecified,
         output_name : str or None or list or dict
             The name of the variable as listed in the phase timeseries outputs.  By
             default this is the last element in `name` when split by dots.  The user may
-            override the constraint name if splitting the path causes name collisions.
+            override the timeseries name if splitting the path causes name collisions.
         units : str or None or _unspecified
             The units to express the timeseries output.  If None, use the
             units associated with the target.  If provided, must be compatible with
@@ -1570,7 +1570,7 @@ def _add_timeseries_output(self, name, output_name=None, units=_unspecified, sha
         output_name : str or None
             The name of the variable as listed in the phase timeseries outputs.  By
             default this is the last element in `name` when split by dots.  The user may
-            override the constraint name if splitting the path causes name collisions.  If rate
+            override the timeseries name if splitting the path causes name collisions.  If rate
             is True, the rate name will be this name + _rate.
         units : str or None
             The units to express the timeseries output.  If None, use the
@@ -1649,7 +1649,7 @@ def add_objective(self, name, loc='final', index=None, shape=(1,), units=None, r
         Add an objective in the phase.
 
         If name is not a state, control, control rate, or 'time', then this is assumed to be the
-        path of the variable to be constrained in the RHS.
+        path of the variable to be optimized.
 
         Parameters
         ----------