Merge pull request #2 from pziegfeld/1_flop_edits

Made editorial changes usage doc.

docs/conf.py

@@ -1,7 +1,7 @@
 
 
-# This file is autogenerated during plugin_quickstart and overwritten during
-# plugin_makedist. DO NOT CHANGE IT if you plan to use plugin_makedist to package
+# This file is autogenerated during plugin quickstart and overwritten during
+# plugin makedist. DO NOT CHANGE IT if you plan to use plugin makedist to package
 # distribution.
 
 # -*- coding: utf-8 -*-

docs/index.rst

@@ -9,7 +9,7 @@ Contents:
 .. toctree::
    :maxdepth: 2
 
-   usage
+   usage.rst
    srcdocs
    pkgdocs
 

docs/usage.rst

@@ -5,15 +5,15 @@ Using the FLOPS Openmdao Wrapper
 The FlopsWrapper component is a file-wrap of FLOPS, or Flight Optimization
 System. This distribution includes the files you need to run FLOPS in
 OpenMDAO. It does not include a source or binary distribution of FLOPS, which
-you are assumed to already have installed in your local environment.
+it is assumed you already have installed in your local environment.
 
 The FlopsWrapper exposes practically every input variable that is editable in
 the standard input file. It also provides a large selection of outputs that it
 parses from the output file. Generally, the variables are grouped according to
-their namelist in the intput file. Please see the source documentation for a
+their namelist in the input file. Please see the source documentation for a
 complete list of variables, with descriptions and values.
 
-FlopsWrapper can be imported from flops_wrapper.py, which should reside in the
+FlopsWrapper can be imported from ``flops_wrapper.py``, which should reside in the
 site-packages directory of your activated Python environment once it is
 installed.
 
@@ -29,18 +29,18 @@ into the openmdao component is to use the ``load_model`` method.
     flops_comp.load_model('my_model.in')
     
 FLOPS input files are Fortran namelists, and OpenMDAO is able to parse a
-namelist file, and import that information into the existing variable
+namelist file and import that information into the existing variable
 structure of the FLOPS wrapper component.
 
 The values can also be loaded manually by assigning each variable
-individually. This is definitely the 'hard way', and will require a bit
-more familiarity with the internals of the wrap. It is possible to
+individually. This is definitely the "hard way" and will require you to be 
+familiar with the internals of the wrap. It is possible to
 add and remove rerun, pconin, and segin groups this way as well.
 
 When you create a new instance of FlopsWrapper, all of the variables are
 initiated with the same default values that FLOPS uses.
 
-If your local FLOPS install is not on your system path, you will need
+If your local FLOPS install is not in your system path, you will need
 to tell OpenMDAO where to find it as per the following example:
 
 ::