deploy: 498b419

Author: hweifluids

.doctrees/6_inputdeck.doctree

@@ -91,7 +91,7 @@
 <p>This section details the solver parameters in the structured input deck (<code class="docutils literal notranslate"><span class="pre">.par</span></code> file), which is finally read by the main solver.
 In GUI mode, it is also the only purpose for the preprocessor to write out, and serves as the mid-file format for GUI resolve.
 It includes the path pointing to data, indicates the path to save results, and determines the modes and numerical methods for the solver.
-In other words, if the data is placed properly, this <code class="docutils literal notranslate"><span class="pre">.par</span></code> it the only input file by the solver.</p>
+In other words, if the data is placed properly, this <code class="docutils literal notranslate"><span class="pre">.par</span></code> is the only input file by the solver.</p>
 <section id="input-and-range-control">
 <h2>Input and Range Control<a class="headerlink" href="#input-and-range-control" title="Link to this heading"></a></h2>
 <table class="docutils align-default">

.doctrees/environment.pickle

@@ -6,7 +6,7 @@ Input Deck for Solver Parameters
 This section details the solver parameters in the structured input deck (``.par`` file), which is finally read by the main solver.
 In GUI mode, it is also the only purpose for the preprocessor to write out, and serves as the mid-file format for GUI resolve.
 It includes the path pointing to data, indicates the path to save results, and determines the modes and numerical methods for the solver.
-In other words, if the data is placed properly, this ``.par`` it the only input file by the solver.
+In other words, if the data is placed properly, this ``.par`` is the only input file by the solver.
 
 
 Input and Range Control