Update verify-install.dita

temporarily updating figure names

cityehr-quick-start-guide/src/main/lwdita/quickstart-guide-modular/verify-install.dita

@@ -27,7 +27,7 @@
             <p><image href="images/post-authentication-page.png" format="image/png"><alt>Post Authentication Page</alt></image>
             </p>
             <p> </p>
-            <p>Press the Start button to move to the default home page, which is pre-configured to be the dashboard page, as shown in <i>Figure 5</i>. </p>
+            <p>Press the Start button to move to the default home page, which is pre-configured to be the dashboard page, as shown in the figure below </p>
             <p>The Dashboard shows a summary of the overall status of the cityEHR application, which ships by default with the base installation. There is one user registered (the 'admin' user you logged in as) and no patients (so the total patients is zero, there are no clinical documents recorded and no documents in progress). </p>
             <note>
                 <p>The number of Information Models shown in the dashboard. If this number is zero (0) then the default application was not loaded properly when you ran cityEHR forthe first time (probably because you selected to "Use Empty Database".</p>
@@ -37,7 +37,7 @@
             </p>
             <p> </p>
             <p>The Dashboard is your first glimpse of the pages in cityEHR, which can either be non-patient (like the Dashboard), cross-patient (the Patient Search page, for example) or patient specific (view of the record for a patient, as identified in the Patient Label) </p>
-            <p>Whichever type, the general layout of all pages in the cityEHR system is the same, as shown in Figure 6. </p>
+            <p>Whichever type, the general layout of all pages in the cityEHR system is the same, as shown in the figure below. </p>
             <p> </p>
             <p><image href="images/system-page-layout.png" format="image/png"><alt>System Page Layout</alt></image>
             </p>
@@ -60,7 +60,7 @@
                     <p>In the Confirmation Dialog, select to Reload </p>
                 </li>
             </ol>
-            <p>Now wait while the models are reloaded (which may take a few minutes) - progress is displayed in the main view. Once completed, the progress display will be cleared and you should see a summary of the models as shown in Figure 7. </p>
+            <p>Now wait while the models are reloaded (which may take a few minutes) - progress is displayed in the main view. Once completed, the progress display will be cleared and you should see a summary of the models as shown in the Figure below. </p>
             <p><image href="images/information-model-summary.png" format="image/png"><alt>Information Model Summary</alt></image></p>
         </section>
         <section id="running-in-debug-mode">
@@ -86,7 +86,7 @@
                     <p>Check the box for Debugging Mode and then press the Save button that will appear on the top right action menu </p>
                 </li>
                 <li>
-                    <p>These steps are illustrated in Figure 8 </p>
+                    <p>These steps are illustrated in the Figure below </p>
                 </li>
                 <li>
                     <p>When operating in debug mode, cityEHR displays some additional action buttons and selections that allow yo uto explore the XML structures that underlie the configuration and clinical content (HL7 CDA) </p>
@@ -112,23 +112,23 @@
                 </li>
             </ol>
             <p>Running in Debug Mode allows the user access to additional features that expose some of the underlying information structures in cityEHR. </p>
-            <p>On the Sign On page, as shown in Figure 9, various of the internal XML instances, built during the log on process, are available to view by selecting in the Debug Info drop
+            <p>On the Sign On page, as shown in the Figure below, various of the internal XML instances, built during the log on process, are available to view by selecting in the Debug Info drop
                 down and then pressing the Debug button. </p>
             <p><image href="images/startup-debug-mode.png" format="image/png"><alt>cityEHR start-up in Debugging mode</alt></image>
             </p>
             <p> </p>
             <p>On patient-specific data input pages (Forms, Letters, etc) pressing the XML button will bring up a dialog box with a listing of the current HL7 CDA document associated with the data input form. This dialog also has a button to Download the HL7 CDA XML. </p>
             <p><image href="images/xml-viewer-das28.png" format="image/png"><alt>XML viewer open for DAS 28 Form</alt></image></p>
             <p> </p>
-            <p>Also on patient-specific data input pages are check boxes to Display ISO 13606 structure (Figure 11) or to show the Identifiers for the ISO 13606 components on the form (Figure 12). </p>
+            <p>Also on patient-specific data input pages are check boxes to Display ISO 13606 structure or to show the Identifiers for the ISO 13606 components on the form. </p>
             <p> </p>
             <p><image href="images/iso13606-structure-debug-mode.png" format="image/png"><alt>Showing ISO 13606 Structure in Debug Mode</alt></image></p>
             <p> </p>
             <p><image href="images/iso13606-ids-debug-mode.png" format="image/png"><alt>Showing ISO 13606 Component Ids in Debug Mode</alt></image></p>
         </section>
         <section id="session-time-out">
             <title>Session Time Out</title>
-            <p>The cityEHR session is set to time out after a period on inactivity – this is controlled by the underlying session management of the Tomcat application server. If such a timeout occurs you will see an error dialogue which allows you to restart the application – see Figure 13. </p>
+            <p>The cityEHR session is set to time out after a period on inactivity – this is controlled by the underlying session management of the Tomcat application server. If such a timeout occurs you will see an error dialogue which allows you to restart the application. </p>
             <p> </p>
             <p><image href="images/session-timeout-dialogue.png" format="image/png"><alt>Session Time Out Dialogue</alt></image>
             </p>