Merge pull request #3988 from blnicho/fix-typos

Fix new typos identified in latest typos release

Author: blnicho

pyomo/common/env.py

@@ -393,7 +393,7 @@ class CtypesEnviron:
     `os.environ` reflects the current python environment variables, and
     will be passed to subprocesses.  However, it does not reflect the C
     Runtime Library (MSVCRT) environment on Windows platforms.  This can
-    be problemmatic as DLLs loaded through the CTYPES interface will see
+    be problematic as DLLs loaded through the CTYPES interface will see
     the MSVCRT environment and not os.environ.  This class provides a
     way to manage environment variables and pass changes to both
     os.environ and the MSVCRT runtime.

pyomo/contrib/pynumero/sparse/block_matrix.py

@@ -761,7 +761,7 @@ def copy(self, deep=True):
 
     def copy_structure(self):
         """
-        Makes a copy of the structure of this BlockMatrix. This proivides a
+        Makes a copy of the structure of this BlockMatrix. This provides a
         light-weighted copy of each block in this BlockMatrix. The blocks in the
         resulting matrix have the same shape as in the original matrices but not
         the same number of nonzeros.

pyomo/contrib/pynumero/sparse/mpi_block_matrix.py

@@ -571,7 +571,7 @@ def copy(self):
 
     def copy_structure(self):
         """
-        Makes a copy of the structure of this MPIBlockMatrix. This proivides a
+        Makes a copy of the structure of this MPIBlockMatrix. This provides a
         light-weighted copy of each block in this MPIBlockMatrix. The blocks in the
         resulting matrix have the same shape as in the original matrices but not
         the same number of nonzeros.

pyomo/core/base/component.py

@@ -516,7 +516,7 @@ def reconstruct(self, data=None):
 
         Re-constructing model components was fragile and did not
         correctly update instances of the component used in other
-        components or contexts (this was particularly problemmatic for
+        components or contexts (this was particularly problematic for
         Var, Param, and Set).  Users who wish to reproduce the old
         behavior of reconstruct(), are comfortable manipulating
         non-public interfaces, and who take the time to verify that the

pyomo/core/base/set.py

@@ -714,7 +714,7 @@ def _get_discrete_interval(self):
         # randomly removing elements from the list; however, since we
         # do it by enumerating over ranges, using set() would make this
         # routine nondeterministic.  Not a huge issue for the result,
-        # but problemmatic for code coverage.
+        # but problematic for code coverage.
         ranges = list(self.ranges())
         if len(ranges) == 1:
             try:
@@ -808,7 +808,7 @@ def _get_continuous_interval(self):
         # randomly removing elements from the list; however, since we
         # do it by enumerating over ranges, using set() would make this
         # routine nondeterministic.  Not a hoge issue for the result,
-        # but problemmatic for code coverage.
+        # but problematic for code coverage.
         #
         # Note: We do not need to trap non-NumericRange objects:
         # RangeProduct and AnyRange will be caught by the dimen test in