updated

ShawnDriscoll · Oct 2, 2017 · 944cbec · 944cbec
1 parent 4649c43
commit 944cbec
Show file tree

Hide file tree

Showing 8 changed files with 6 additions and 6 deletions.
diff --git a/docs/build/.doctrees/debugging.doctree b/docs/build/.doctrees/debugging.doctree
diff --git a/docs/build/.doctrees/environment.pickle b/docs/build/.doctrees/environment.pickle
diff --git a/docs/build/_sources/debugging.txt b/docs/build/_sources/debugging.txt
@@ -24,7 +24,7 @@ Changing **diceroll's** logging mode to ``DEBUG`` will record debugging messages
    Sun, 01 Oct 2017 16:27:21 INFO diceroll - 3D4 = 3D4+0 = 8
 
 .. note::
-   Running **diceroll** in ``DEBUG`` mode may create a log while that will be too huge to open. A program of yours
+   Running **diceroll** in ``DEBUG`` mode may create a log file that will be too huge to open. A program of yours
    left running for a long period of time could create millions of lines of recorded log entries. Fortunately, ``diceroll.log`` is
    reset each time your program is run. Also, any errors encountered will be recorded as ``ERROR`` in the log file, no
    matter which logging mode you've chosen to use.

diff --git a/docs/build/debugging.html b/docs/build/debugging.html
@@ -67,7 +67,7 @@ <h1><strong>Debugging diceroll</strong><a class="headerlink" href="#debugging-di
 Sun, 01 Oct 2017 16:27:21 INFO diceroll - 3D4 = 3D4+0 = 8</pre>
 <div class="admonition note">
 <p class="first admonition-title">Note</p>
-<p class="last">Running <strong>diceroll</strong> in <tt class="docutils literal"><span class="pre">DEBUG</span></tt> mode may create a log while that will be too huge to open. A program of yours
+<p class="last">Running <strong>diceroll</strong> in <tt class="docutils literal"><span class="pre">DEBUG</span></tt> mode may create a log file that will be too huge to open. A program of yours
 left running for a long period of time could create millions of lines of recorded log entries. Fortunately, <tt class="docutils literal"><span class="pre">diceroll.log</span></tt> is
 reset each time your program is run. Also, any errors encountered will be recorded as <tt class="docutils literal"><span class="pre">ERROR</span></tt> in the log file, no
 matter which logging mode you&#8217;ve chosen to use.</p>

diff --git a/docs/build/modindex.html b/docs/build/modindex.html
@@ -20,7 +20,7 @@
     <link rel="index" title="Global index" href="genindex.html" />
     <link rel="search" title="Search" href="search.html" />
     <link rel="top" title="diceroll 2.2 Manual" href="index.html" />
-<generator object at 0x035F90A8>
+<generator object at 0x03844198>
 
     <script type="text/javascript">
       DOCUMENTATION_OPTIONS.COLLAPSE_MODINDEX = true;

diff --git a/docs/build/search.html b/docs/build/search.html
@@ -20,7 +20,7 @@
     <link rel="index" title="Global index" href="genindex.html" />
     <link rel="search" title="Search" href="" />
     <link rel="top" title="diceroll 2.2 Manual" href="index.html" />
-<generator object at 0x036AF328>
+<generator object at 0x0378B878>
     <script type="text/javascript" src="_static/searchtools.js"></script>
 
   </head>

diff --git a/docs/build/searchindex.json b/docs/build/searchindex.json
diff --git a/docs/source/debugging.rst b/docs/source/debugging.rst
@@ -24,7 +24,7 @@ Changing **diceroll's** logging mode to ``DEBUG`` will record debugging messages
    Sun, 01 Oct 2017 16:27:21 INFO diceroll - 3D4 = 3D4+0 = 8
    
 .. note::
-   Running **diceroll** in ``DEBUG`` mode may create a log while that will be too huge to open. A program of yours
+   Running **diceroll** in ``DEBUG`` mode may create a log file that will be too huge to open. A program of yours
    left running for a long period of time could create millions of lines of recorded log entries. Fortunately, ``diceroll.log`` is
    reset each time your program is run. Also, any errors encountered will be recorded as ``ERROR`` in the log file, no
    matter which logging mode you've chosen to use.