install: Write some of chapter 5

1 files changed, 2 insertions, 2 deletions

diff --git a/src/install/7_scripts.xml b/src/install/7_scripts.xml
index 3ea0550..c21855a 100644
--- a/src/install/7_scripts.xml
+++ b/src/install/7_scripts.xml
@@ -111,7 +111,7 @@ inherit cad.installfile
             <step><para>Open a Terminal window.</para></step>
             <step><para>Run <literal><command>hscript-validate</command> <filename><userinput>/path/to/installfile</userinput></filename></literal>, where <userinput>/path/to/installfile</userinput> is the path to your HorizonScript.</para></step>
         </procedure>
-        <para>The HorizonScript Validation Utility outputs log messages in the same format as the Horizon Executor.  For more information on interpreting log messages from the HorizonScript Validation Utility, refer to <!-- TODO chap 5 <xref linkend="executor_log"/> -->.</para>
+        <para>The HorizonScript Validation Utility outputs log messages in the same format as the Horizon Executor.  For more information on interpreting log messages from the HorizonScript Validation Utility, refer to <xref linkend="executor_log"/>.</para>
         <para>If you believe your HorizonScript may have multiple errors, you can use the <option>-k</option> flag (which stands for "Keep going") to have the Validation Utility run through the entire script instead of stopping at the first error.</para>
     </section>
     <section id="simulate_script">
@@ -123,7 +123,7 @@ inherit cad.installfile
             <step><para>Open a Terminal window.</para></step>
             <step><para>Run <literal><command>hscript-simulate</command> <filename><userinput>/path/to/installfile</userinput></filename></literal>, where <userinput>/path/to/installfile</userinput> is the path to your HorizonScript.</para></step>
         </procedure>
-        <para>The HorizonScript Simulation Utility outputs log messages in the same format as the Horizon Executor.  For more information on interpreting log messages from the HorizonScript Simulation Utility, refer to <!-- TODO chap 5 <xref linkend="executor_log"/> -->.</para>
+        <para>The HorizonScript Simulation Utility outputs log messages in the same format as the Horizon Executor.  For more information on interpreting log messages from the HorizonScript Simulation Utility, refer to <xref linkend="executor_log"/>.</para>
         <para>The HorizonScript Simulation Utility writes log messages to <literal>stderr</literal>, and the equivalent shell commands to <literal>stdout</literal>.  If you want to read the log messages and discard the shell commands, you may run the <literal><command>hscript-simulate</command></literal> command with <literal>stdout</literal> redirected to <literal>/dev/null</literal>, as in <literal><command>hscript-simulate</command> <filename><userinput>/path/to/installfile</userinput></filename> &gt;/dev/null</literal>.  Similarly, if you want to save the shell commands to a file, you may redirect <literal>stdout</literal> to a file, as in <literal><command>hscript-simulate</command> <filename><userinput>/path/to/installfile</userinput></filename> &gt;<userinput>myscript.sh</userinput></literal>.</para>
     </section>
 </chapter>