[education/kstars] doc: Increase visibility for Ekos and FITS Viewer in the KStars Handbook

Hy Murveit null at kde.org
Tue Dec 5 05:31:36 GMT 2023


Git commit d694512d85b334287b832ab3609a20f76f6ec724 by Hy Murveit.
Committed on 05/12/2023 at 06:31.
Pushed by murveit into branch 'master'.

Increase visibility for Ekos and FITS Viewer in the KStars Handbook

Modifies the handbook so that Ekos and FITS Viewer become full-fledged chapters (instead of subsections inside of KStars/tools). I also made minor revisions to the abstract and introduction sections.

M  +2    -2    doc/commands.docbook
M  +3    -3    doc/config.docbook
M  +38   -38   doc/ekos-align.docbook
M  +8    -8    doc/ekos-analyze.docbook
M  +25   -25   doc/ekos-capture.docbook
M  +50   -50   doc/ekos-focus.docbook
M  +25   -25   doc/ekos-guide.docbook
M  +2    -2    doc/ekos-logs.docbook
M  +2    -2    doc/ekos-profile-editor.docbook
M  +2    -2    doc/ekos-profile-wizard.docbook
M  +34   -34   doc/ekos-scheduler.docbook
M  +2    -2    doc/ekos-setup.docbook
M  +3    -3    doc/ekos-tutorials.docbook
M  +2    -2    doc/ekos-user-interface.docbook
M  +3    -5    doc/ekos.docbook
M  +18   -20   doc/fitsviewer.docbook
M  +43   -23   doc/index.docbook
M  +1    -1    doc/indi.docbook
M  +3    -3    doc/quicktour.docbook
M  +0    -4    doc/tools.docbook

https://invent.kde.org/education/kstars/-/commit/d694512d85b334287b832ab3609a20f76f6ec724

diff --git a/doc/commands.docbook b/doc/commands.docbook
index 721a4cef01..c677992166 100644
--- a/doc/commands.docbook
+++ b/doc/commands.docbook
@@ -17,7 +17,7 @@
 <guimenu>File</guimenu>
 <guimenuitem>Open Image...</guimenuitem>
 </menuchoice></term>
-<listitem><para>Open an image in the FITS Viewer tool.
+<listitem><para>Open an image in the FITS Viewer.
 </para></listitem>
 </varlistentry>
 
@@ -550,7 +550,7 @@ current simulation date.
 </menuchoice></term>
 <listitem>
 <para>
-Opens <link linkend="tool-ekos">Ekos</link>, a complete and powerful tool for astrophotography.
+Opens <link linkend="ekos">Ekos</link>, a complete and powerful tool for astrophotography.
 With Ekos, you can align and guide your telescope, focus your CCD, and capture
 images using an easy intuitive interface.
 </para>
diff --git a/doc/config.docbook b/doc/config.docbook
index 5568d3eb88..f3c2f225dc 100644
--- a/doc/config.docbook
+++ b/doc/config.docbook
@@ -238,7 +238,7 @@ page see the <link linkend="indi-configure">Configure INDI</link> section.
 
 <!-- Ekos page: -->
 <para>For detailed explanation of <guilabel>Ekos</guilabel> astrophotography suite,
-see the <link linkend="tool-ekos">Ekos section of this manual</link>.
+see the <link linkend="ekos">Ekos section of this manual</link>.
 </para>
 
 <!-- Xplanet page: -->
@@ -1367,7 +1367,7 @@ page see the <link linkend="indi-configure">Configure INDI</link> section.
 </para>
 </sect1>
 
-<sect1 id="ekos">
+<sect1 id="ekos-window">
 <title>Ekos</title>
 <screenshot>
 <screeninfo>Ekos Window</screeninfo>
@@ -1386,7 +1386,7 @@ all INDI devices including numerous telescopes, CCDs, DSLRs, focusers, filters,
 Ekos supports highly accurate tracking using online and offline astrometry solver, autofocus
 and autoguiding capabilities, and capture of single or multiple images using the powerful
 built in sequence manager. For detailed explanation of <guilabel>Ekos</guilabel>,
-see the <link linkend="tool-ekos">Ekos section of this manual</link>.
+see the <link linkend="ekos">Ekos section of this manual</link>.
 </para>
 </sect1>
 
diff --git a/doc/ekos-align.docbook b/doc/ekos-align.docbook
index c96274eacf..83e7820327 100644
--- a/doc/ekos-align.docbook
+++ b/doc/ekos-align.docbook
@@ -1,11 +1,11 @@
-<sect2 id="ekos-align">
+<sect1 id="ekos-align">
     <title>Align</title>
     <indexterm>
         <primary>Tools</primary>
         <secondary>Ekos</secondary>
         <tertiary>Align</tertiary>
     </indexterm>
-    <sect3 id="ekos-align-introduction">
+    <sect2 id="ekos-align-introduction">
         <title>Introduction</title>
         <screenshot>
             <screeninfo>
@@ -32,9 +32,9 @@
         <para>
             At a minimum, you need a CCD/Webcam and a telescope that supports Slew & Sync commands. Most popular commercial telescope nowadays support such commands.
         </para>
-    </sect3>
+    </sect2>
 
-        <sect3 id="ekos-align-typical">
+        <sect2 id="ekos-align-typical">
             <title>Typical use</title>
             <para>
                 Using Ekos Alignment Module, aligning your mount using the controller's 1, 2, or 3 star alignment is <emphasis>not</emphasis> strictly necessary, though for some mounts it is recommended to perform a rough 1 or 2 star alignment before using Ekos alignment module. If you are using EQMod, you can start using Ekos alignment module right away. A typical workflow for GOTO alignment involves the following steps:
@@ -89,9 +89,9 @@
                     </para>
                 </listitem>
             </itemizedlist>
-        </sect3>
+        </sect2>
     
-    <sect3 id="ekos-solver-options">
+    <sect2 id="ekos-solver-options">
       <title>Configure StellarSolver Options </title>
         <screenshot>
             <screeninfo>
@@ -112,9 +112,9 @@
       <para>
         There are two other minor options. <guilabel>WCS</guilabel> or  World-Coordinate-System is a system for embedding equatorial coordinate information within the image. When you view a solved image, you can hover it and view the coordinate for each pixel. You can also click anywhere in the image and command to the telescope to slew there. It is highly recommended to keep this option on. <guilabel>Overlay</guilabel> overlays captured images unto the sky map of &kstars;.
         </para>
-    </sect3>
+    </sect2>
     
-    <sect3 id="ekos-solver-external">
+    <sect2 id="ekos-solver-external">
       <title>Configure StellarSolver External Programs </title>
         <screenshot>
             <screeninfo>
@@ -135,9 +135,9 @@
       <para>
         You will need to make sure the paths are correct for the solver you choose. The top menu item <guilabel>select to load one of the default sets</guilabel> usually configures the boxes correctly.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-solver-scale">
+    <sect2 id="ekos-solver-scale">
       <title>Configure StellarSolver Scale and Position </title>
         <screenshot>
             <screeninfo>
@@ -157,9 +157,9 @@
         </para><para>Scale can be the image width in degrees (<guilabel>dw</guilabel>), the image width in arc-minutes (<guilabel>aw</guilabel>), or the pixel width in arc-seconds (<guilabel>app</guilabel>). All should work, but arc-seconds per pixel is recommended. Typically you want to use this constraint for faster solving, so we recommend you check this box. The system doesn't require that the scale be exactly right--it allows deviations of 10-20%. However, frequently issues related to solving are due to an inaccurate scale being used. Therefore, if you have plate-solving problems, you may want to uncheck <guilabel>Use Scale</guilabel> until those issues are resolved. This will likely result in longer solving times. <guilabel>Auto-update</guilabel> will automatically fill the scale box with the scale found in the most-recent successful solve.
         </para><para>The RA and DEC positions are usually filled in from the position the telescope thinks it is pointing. Naturally, the system doesn't require an exactly correct positional constraint--afterall the purpose of plate-solving is to find that position. The maximum distance in degrees from the specified position to the actual position is given by the <guilabel>Radius</guilabel> field. Plate-solving will fail if the specified position is further away.  Typically you want to enable <guilabel>Use Position</guilabel> for faster solving, so we recommend you check this box. However, frequently issues related to solving are due to using a poor positional estimate (e.g. the telescope is significantly misaligned). Therefore, if you have plate-solving problems, you may want to uncheck <guilabel>Use Position</guilabel> until those issues are resolved. As mentioned, this will result in longer solving times. <guilabel>Auto-update</guilabel> will fill the position box with the position found in the most-recent successful solve. However, a slew will update the position to the position where the telescope thinks it is pointing after the slew.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-align-profiles">
+    <sect2 id="ekos-align-profiles">
       <title>Configure StellarSolver Profiles </title>
         <screenshot>
             <screeninfo>
@@ -189,7 +189,7 @@
           All the input fields have tooltips that are displayed if you hover your mouse over the input box.
           </para><para>You can make changes to the values and save the profile if you like, or restore the profile's original values.
           </para>
-        <sect4 id="profile-star-extraction">
+        <sect3 id="profile-star-extraction">
           <title>Star-Extraction Parameters</title>
           <para>
             The column headings are links to the Sextractor manual which is the main source for these parameters. View those links to find details on all the parameters. We will touch upon some of the parameters you might consider adjusting. However, it's probably best not to get into the weeds of modifying most of these values.
@@ -199,9 +199,9 @@
          <listitem><para><guilabel>Min Area</guilabel> is the minimum area for a star detection--area is in square pixels where all pixels have higher-than-threshold pixel values. If you are detecting small noise spikes as stars, you might want to increase this. If you are not detecting desired smaller real stars, perhaps your <guilabel>Min Area</guilabel> is too high.</para></listitem>
          <listitem><para><guilabel>Conv FWHM</guilabel> should be adjusted to roughly the seeing in your area in pixels. The image is smoothed by this amount before star detection is initiated.</para></listitem>
         </itemizedlist>
-        </sect4>    
+        </sect3>    
 
-        <sect4 id="profile-star-filtering">
+        <sect3 id="profile-star-filtering">
         <title>Star-Filtering Parameters</title>
           <para>
             This filtering is done for the sake of speed mostly, as well as for removing clipped stars, or very elliptical objects which might be galaxies. We will touch upon some of the parameters you might consider adjusting. Zero values for these parameters disable the filter. However, once again it's probably best not to get into the weeds of modifying most of these values.
@@ -212,9 +212,9 @@
          <listitem><para><guilabel>Max Ellipse</guilabel> specifies how elliptical a star can be before being removed. 2 would mean the larger axis could be twice as large as the smaller axis.</para></listitem>
          <listitem><para><guilabel>Cut Brightest</guilabel> and <guilabel>Cut Dimmest</guilabel> remove the X% brightest or dimmest stars from consideration. <guilabel>Sat Limit</guilabel> removes stars whose pixel values exceed that percentage of the maximum pixel value--to remove saturated stars.</para></listitem>
              </itemizedlist>
-        </sect4>
+        </sect3>
 
-        <sect4 id="profile-plate-solving">
+        <sect3 id="profile-plate-solving">
           <title>Plate-Solving Parameters</title>
           <para>
             These plate-solving parameters mostly relate to computation resources.
@@ -223,10 +223,10 @@
          <listitem><para><guilabel>Search Radius</guilabel> is the distance from the position estimate in degrees that may be searched if <guilabel>Use Position</guilabel> is checked. </para></listitem>
          <listitem><para><guilabel>Maximum Time</guilabel> is the maximum number of seconds that the plate-solving will run before it times out.</para></listitem>
              </itemizedlist>
-        </sect4>    
-    </sect3>    
+        </sect3>    
+    </sect2>    
     
-    <sect3 id="ekos-align-download-index-files">
+    <sect2 id="ekos-align-download-index-files">
       <title>Download Index Files</title>
       <para>
         Index files are required if you choose the <guilabel>Internal Solver</guilabel> or <guilabel>Local Astrometry</guilabel> <guilabel>Solving Method</guilabel>.
@@ -234,7 +234,7 @@
         <para>
             For offline (and remote) solvers, index files are necessary for the solver to work. The complete collection of index files is huge (over 30 GB), but you only need to download what is necessary for your equipment setup. Index files are sorted by the Field-Of-View (FOV) range they cover. There are two methods to fetch the necessary index files: The new download support in Align module, and the old manual way.
         </para>
-        <sect4 id="ekos-align-automatic-download">
+        <sect3 id="ekos-align-automatic-download">
             <title>Automatic Download</title>
             <screenshot>
                 <screeninfo>
@@ -275,8 +275,8 @@
             <para>
                 You must download all the required files, and if you have plenty of hard drive space left, you can also download the recommended indexes. If an index file is installed, the checkmark shall be checked, otherwise check it to download the relevant index file. Please only download one file at a time, especially for larger files. You might be prompted to enter the administrator password (default in StellarMate is <userinput>smate</userinput>) to install the files. Once you installed all the required files, you can begin using the offline astrometry.net solver immediately.
             </para>
-        </sect4>
-        <sect4 id="ekos-align-manual-download">
+        </sect3>
+        <sect3 id="ekos-align-manual-download">
                 <title>Manual Download</title>
                 <para>
                     You need to <ulink url="http://data.astrometry.net">download</ulink> and install the necessary index files suitable for your telescope+CCD field of view (FOV). You need to install index files covering 100% to 10% of your FOV. For example, if your FOV is 60 arcminutes, you need to install index files covering skymarks from 6 arcminutes (10%) to 60 arcminutes (100%). There are many online tools to calculate FOVs, such as <ulink url="http://starizona.com/acb/ccd/calc_pixel.aspx">Starizona Field of View Calculator</ulink>.
@@ -398,10 +398,10 @@
                         It is recommended to use a download manager as such <ulink url="https://addons.mozilla.org/en-US/firefox/addon/downthemall/">DownThemAll!</ulink> for &firefox; to download the Debian packages as browsers' built-in download manager may have problems with download large packages.
                     </para>
                 </note>
-            </sect4>
-        </sect3>
+            </sect3>
+        </sect2>
 
-    <sect3 id="ekos-align-get-astrometry">
+    <sect2 id="ekos-align-get-astrometry">
         <title>Optionally get astrometry.net</title>
 
         <para>
@@ -476,9 +476,9 @@
                 </listitem>
             </varlistentry>
         </variablelist>
-    </sect3>
+    </sect2>
     
-        <sect3 id="ekos-align-how-to-use">
+        <sect2 id="ekos-align-how-to-use">
             <title>How to Use?</title>
             <para>
                 Ekos Align Module offers multiple functions to aid you in achieving accurate GOTOs. For some mounts it is useful to start your session with your mount in home position with the telescope tube looking directly at the celestial pole. For users in Northern Hemisphere, point the telescope as close as possible to Polaris. It is not necessary to perform 2 or 3 star alignments, but it can be useful for some mount types. Make sure your camera is focused.
@@ -503,9 +503,9 @@
                     <emphasis role="bold">Never</emphasis> solve an image at or near the celestial pole (unless Ekos Polar Alignment Assistant Tool is used). Slew at least 20 degrees away from the celestial pole before solving the first image. Solving very close to the poles will make your mount pointing worse, so avoid it.
                 </para>
             </warning>
-        </sect3>
+        </sect2>
         
-        <sect3 id="ekos-align-alignment-settings">
+        <sect2 id="ekos-align-alignment-settings">
             <title>Alignment Settings</title>
             <para>
                 Before you begin the alignment process, select the desired optical train. You can explore astrometry.net options that are passed to the astrometry.net solver each time an image is captured:
@@ -547,9 +547,9 @@
                     </para>
                 </listitem>
             </itemizedlist>
-        </sect3>
+        </sect2>
 
-        <sect3 id="ekos-align-polaralignment">
+        <sect2 id="ekos-align-polaralignment">
             <title>Polar Alignment</title>
                 <para>
                     When setting up a German Equatorial Mount (GEM) for imaging, a critical aspect of capturing long-exposure images is to ensure proper polar alignment. A GEM mount has two axis: Right Ascension (RA) axis and Declination (DE) axis. Ideally, the RA axis should be aligned with the celestial sphere polar axis. A mount's job is to track the star's motion around the sky, from the moment they rise at the eastern horizon, all the way up across the median, and westward until they set.
@@ -608,7 +608,7 @@
                     </mediaobject>
                 </screenshot>
 
-            <sect4 id="ekos-align-platesolvecorrection">
+            <sect3 id="ekos-align-platesolvecorrection">
                 <title>Plate Solve Correction Scheme</title>
                 
                 <para>
@@ -665,8 +665,8 @@
                         </textobject>
                     </mediaobject>
                 </screenshot>
-                </sect4>
-                <sect4 id="ekos-align-move-star-correction">
+                </sect3>
+                <sect3 id="ekos-align-move-star-correction">
                 <title>Move Star Correction Scheme</title>
 
                 <para>
@@ -676,6 +676,6 @@
                     The difference between <emphasis>Move Star & Calc Error</emphasis> and  <emphasis>Move Star</emphasis> is that in the former, the system attempts to track the star the user has selected, and places a circle around that star. In that scheme it also attempts to update the <emphasis>Updated Err</emphasis> row. If the star tracking isn't reliable, simply ignore it or use the <emphasis> Move Star </emphasis>scheme and move the star by-eye until it's close to the final target. An example of using this technique is shown in this video: 
                     <ulink url="https://www.youtube.com/watch?v=iOp7hrxw0oU">https://www.youtube.com/watch?v=iOp7hrxw0oU</ulink>
                 </para>
-            </sect4>
-        </sect3>
-</sect2>
+            </sect3>
+        </sect2>
+</sect1>
diff --git a/doc/ekos-analyze.docbook b/doc/ekos-analyze.docbook
index 008870e9b0..cb7e8b3431 100644
--- a/doc/ekos-analyze.docbook
+++ b/doc/ekos-analyze.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-analyze">
+<sect1 id="ekos-analyze">
     <title>Analyze</title>
     <indexterm>
         <primary>Tools</primary>
@@ -18,7 +18,7 @@
             </textobject>
         </mediaobject>
     </screenshot>
-    <sect3 id="analyze-Introduction">
+    <sect2 id="analyze-Introduction">
         <title>Introduction</title>
         <para>
             The Analyze Module records and displays what happened in an imaging session. That is, it does not control any if your imaging, but rather reviews what occurred. Sessions are stored in an <filename class="directory">analyze</filename> folder, a sister folder to the main logging folder. The <literal role="extension">.analyze</literal> files written there can be loaded into the <guilabel>Analyze</guilabel> tab to be viewed. <guilabel>Analyze</guilabel> also can display data from the current imaging session.
@@ -29,8 +29,8 @@
         <para>
             The three main displays can be hidden to make more room for the other displays. There are checkboxes to the left of the section titles (Timeline, Statistics, and Details) that enable and hide the displays.
         </para>
-    </sect3>
-    <sect3 id="analyze-timeline">
+    </sect2>
+    <sect2 id="analyze-timeline">
         <title>Timeline</title>
         <para>
         Timeline shows the major Ekos processes, and when they were active. For instance, the <guilabel>Capture</guilabel> line shows when images were taken (wither green for RGB or color-coded by the filter) and when imaging was aborted (shown as red sections). Clicking on a capture section gives information about that image, and double clicking on one brings up the image taken then in a fitsviewer, if it is available.
@@ -43,8 +43,8 @@
         <para>
             Clicking on a <guilabel>Focus</guilabel> segment shows focus session information and displays up the position vs HFR measurements from that session. Clicking on a <guilabel>Guider</guilabel> segment shows a drift plot from that session, (if it's guiding) and the session's RMS statistics. Other timelines show status information when clicked.
         </para>
-    </sect3>
-    <sect3 id="analyze-statistics">
+    </sect2>
+    <sect2 id="analyze-statistics">
         <title>Statistics</title>
         <para>
           A variety of statistics can be displayed on the <guilabel>Statistics</guilabel> graph. There are too many for all to be shown in a readable way, so select among them with the checkboxes. A reasonable way to start might be to use <guilabel>rms</guilabel>, <guilabel>snr</guilabel> (using the internal guider with SEP Multistar), and <guilabel>hfr</guilabel> (if you have auto-compute HFR in the FITS options). Experiment with others.
@@ -55,5 +55,5 @@
         <para>
           The statistic shown on the left axis can also be scaled (awkwardly) using the mouse <mousebutton>wheel</mousebutton>. It can be panned by dragging the mouse up or down over the left axis' numbers.  Clicking anywhere inside the Statistics graph fills in the values of the displayed statistics. Checking the latest box causes the most recent values (from a live session) to be the statistics displayed. This graph is zoomed and panned horizontally in coordination with the timeline.
         </para>
-    </sect3>
-</sect2>
+    </sect2>
+</sect1>
diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 3f48da3f16..c510993435 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-capture">
+<sect1 id="ekos-capture">
     <title>Capture</title>
     <indexterm>
         <primary>Tools</primary>
@@ -21,7 +21,7 @@
     <para>
         The Capture Module is your primary image and video acquisition module in Ekos. It enables you to capture single (Preview), multiple images (Sequence Queue), or record <ulink url="https://sites.google.com/site/astropipp/ser-player">SER</ulink> videos along with a selection of filter wheel and rotator, if available.
     </para>
-    <sect3 id="capture-ccd-filter-wheel">
+    <sect2 id="capture-ccd-filter-wheel">
         <title>CCD & Filter Wheel Group</title>
         <para>
             Select the desired CCD/DSLR and Filter Wheel (if available) for capture. Set CCD temperature and filter settings.
@@ -43,8 +43,8 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
-    <sect3 id="capture-settings">
+    </sect2>
+    <sect2 id="capture-settings">
         <title>Capture Settings</title>
         <screenshot>
             <screeninfo>
@@ -119,7 +119,7 @@
                 </para>
             </listitem>
         </itemizedlist>
-        <sect4 id="capture-custom-properties">
+        <sect3 id="capture-custom-properties">
             <title>Custom Properties</title>
             <para>
                 Many cameras offer additional properties that cannot be directly set in the capture settings using the common control. The capture controls described above represent the most common settings shared among different cameras, but each camera is unique and may offer its own extended properties. While you can use INDI Control Panel to set any property in the driver; it is important to be able to set such property for each job in the sequence. When you click <guibutton>Custom Properties</guibutton>, a dialog is shown divided into <guilabel>Available Properties</guilabel> and <guilabel>Job Properties</guilabel>. When you move an <guilabel>Available Properties</guilabel> to the <guilabel>Job Property</guilabel> list, its current value can be recorded once you click <guibutton>Apply</guibutton>. When you add a job to the <guilabel>Sequence Queue</guilabel>, the properties values selected in the <guilabel>Job Properties</guilabel> list shall be recorded and saved.
@@ -137,10 +137,10 @@
                     </para>
                 </caption>
             </mediaobject>
-        </sect4>
-    </sect3>
+        </sect3>
+    </sect2>
 
-    <sect3 id="capture-file-settings">
+    <sect2 id="capture-file-settings">
         <title>File Settings</title>
 
         <screenshot>
@@ -271,9 +271,9 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="capture-limit-settings">
+    <sect2 id="capture-limit-settings">
         <title>Limit Settings</title>
 
         <screenshot>
@@ -306,9 +306,9 @@
                     <guilabel>Meridian Flip</guilabel>: If supported by the mount, set the hour angle limit (in hours) before a <ulink url="https://astronomy.mdodd.com/gem_movement.html">meridian flip</ulink> is commanded. For example, if you set the meridian flip duration to 0.1 hours, Ekos shall wait until the mount passes the meridian by 0.1 hours (6 minutes), then it commands the mount to perform a meridian flip. After the meridian flip is complete, Ekos re-aligns using astrometry.net (if <link linkend="ekos-align">the alignment</link> was used) and resumes guiding (if it was started before) and then resumes the capture process automatically.</para>
             </listitem>
         </itemizedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="capture-sequence-queue">
+    <sect2 id="capture-sequence-queue">
         <title>Sequence Queue</title>
 
         <para>
@@ -356,13 +356,13 @@
                 </para>
             </caption>
         </mediaobject>
-    </sect3>
+    </sect2>
 
-    <sect3 id="capture-fits-viewer">
+    <sect2 id="capture-fits-viewer">
         <title>FITS Viewer</title>
 
         <para>
-            Captured images are displayed in &kstars; FITS Viewer tool, and also in the summary screen. Set options related to how the images are displayed in the viewer.
+            Captured images are displayed in &kstars; FITS Viewer, and also in the summary screen. Set options related to how the images are displayed in the viewer.
         </para>
         <itemizedlist>
             <listitem>
@@ -376,9 +376,9 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="capture-rotation-settings">
+    <sect2 id="capture-rotation-settings">
         <title>Rotator Settings</title>
 
         <screenshot>
@@ -416,9 +416,9 @@
         <para>
             Each capture job may be assigned different rotator angles, but be aware that this would cause guiding to abort as it would lose track of the guide star when rotating. Therefore, for most sequences, the rotator angle is kept the same for all capture jobs.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="capture-calibration-frames">
+    <sect2 id="capture-calibration-frames">
         <title>Calibration Frames</title>
 
         <screenshot>
@@ -484,8 +484,8 @@
         <para>
             Before the calibration capture process is started, you can request Ekos to park the mount and/or dome. Depending on your flat source selection above, Ekos will use the appropriate flat light source before starting flat frames capture. If ADU is specified, Ekos begins by capturing a couple of preview images to establish the curve required to achieve the desired ADU count. Once an appropriate value is calculated, another capture is taken and ADU is recounted until a satisfactory value is achieved.
         </para>
-    </sect3>
-    <sect3 id="capture-exposure-calculator">
+    </sect2>
+    <sect2 id="capture-exposure-calculator">
         <title>Exposure Calculator</title>
         <screenshot>
             <screeninfo>
@@ -698,9 +698,9 @@ Part of the value of using a Time/Noise ratio as the input for the calculation o
            </listitem>
         </orderedlist>
 
-        </sect3>
+        </sect2>
 
-    <sect3 id="capture-video-tutorials">
+    <sect2 id="capture-video-tutorials">
         <title>Video Tutorials</title>
 
         <mediaobject>
@@ -724,5 +724,5 @@ Part of the value of using a Time/Noise ratio as the input for the calculation o
                 </para>
             </caption>
         </mediaobject>
-    </sect3>
-</sect2>
+    </sect2>
+</sect1>
diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 459e9a4d46..39fd1d75f6 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<sect2 id="ekos-focus">
+<sect1 id="ekos-focus">
   <title>Focus</title>
 
   <indexterm>
@@ -10,7 +10,7 @@
     <tertiary>Focus</tertiary>
   </indexterm>
 
-  <sect3 id="focus-theory">
+  <sect2 id="focus-theory">
     <title>Theory Of Operation</title>
 
     <screenshot>
@@ -194,9 +194,9 @@
         </itemizedlist>
       </listitem>
     </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="optical-train-group">
+  <sect2 id="optical-train-group">
     <title>Optical Train Group</title>
 
     <screenshot>
@@ -232,9 +232,9 @@
     </itemizedlist>
 
     <para> Focus parameters are saved per Optical Train automatically.</para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-focuser-group">
+  <sect2 id="focus-focuser-group">
     <title>Focuser Group</title>
 
     <screenshot>
@@ -347,9 +347,9 @@
     get familiar with your equipment in daylight. This includes getting the
     approximate focus position on a distant object. This will provide a good
     starting position for focusing on stars when nighttime comes.</para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-ccd-filter-wheel">
+  <sect2 id="focus-ccd-filter-wheel">
     <title>Camera & Filter Wheel Group</title>
 
     <screenshot>
@@ -454,9 +454,9 @@
         subframe to full frame.</para>
       </listitem>
     </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-settings">
+  <sect2 id="focus-settings">
     <title>Focus Settings</title>
 
     <screenshot>
@@ -660,9 +660,9 @@
         </para>
       </listitem>
     </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-process">
+  <sect2 id="focus-process">
     <title>Focus Process</title>
 
     <screenshot>
@@ -987,9 +987,9 @@
         </itemizedlist>
       </listitem>
     </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-mechanics">
+  <sect2 id="focus-mechanics">
     <title>Focus Mechanics</title>
 
     <screenshot>
@@ -1137,9 +1137,9 @@
     to a high enough value that it will not occur during normal operation.</para>
   </listitem>
   </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-cfz">
+  <sect2 id="focus-cfz">
     <title>Focus Critical Focus Zone (CFZ)</title>
 
     <screenshot>
@@ -1290,10 +1290,10 @@
   </listitem>
 
   </itemizedlist>
-  </sect3>
+  </sect2>
 
 
-  <sect3 id="focus-advisor">
+  <sect2 id="focus-advisor">
     <title>Focus Advisor</title>
 
     <screenshot>
@@ -1373,9 +1373,9 @@
     </listitem>
 
   </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-filter-settings">
+  <sect2 id="focus-filter-settings">
       <title>Filter Settings</title>
 
       <screenshot>
@@ -1547,10 +1547,10 @@
               the focuser moves to the Lum Autofocus run solution then in by 100.</para>
           </listitem>
       </itemizedlist>
-  </sect3>
+  </sect2>
 
 
-  <sect3 id="build-filter-offsets">
+  <sect2 id="build-filter-offsets">
       <title>Build Offsets</title>
 
       <screenshot>
@@ -1764,9 +1764,9 @@
             <listitem><para> When happy, press Save to save the filter offsets to Filter Settings for future use.</para></listitem>
             </itemizedlist>
       </para>
-</sect3>
+</sect2>
 
-  <sect3 id="focus-display">
+  <sect2 id="focus-display">
     <title>Focus Display</title>
 
     <screenshot>
@@ -1832,9 +1832,9 @@
         <para> <guibutton>View Star Profile</guibutton>: Launches the View Star Profile dialog.</para>
       </listitem>
     </itemizedlist>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-v-curve">
+  <sect2 id="focus-v-curve">
     <title>V-Curve</title>
 
     <screenshot>
@@ -1935,9 +1935,9 @@
         </textobject>
       </mediaobject>
     </screenshot>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-relative-profile">
+  <sect2 id="focus-relative-profile">
     <title>Relative Profile</title>
 
     <screenshot>
@@ -1962,9 +1962,9 @@
     Finally, the magenta curve denotes the first measured HFR. This enables
     you to judge how well the Autofocus process improved the relative focus
     quality. </para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="How_to_Setup_for_an_Auto_Focus_Run">
+  <sect2 id="How_to_Setup_for_an_Auto_Focus_Run">
     <title>How to Setup for an Autofocus Run</title>
 
     <para> The exact settings that work best for a given astronomical setup need to be worked out by the user using trial and error.
@@ -2005,9 +2005,9 @@
     <screenshot><screeninfo> Bad Focus Curve </screeninfo><mediaobject><imageobject>
     <imagedata fileref="focus_bad_focus.png" format="PNG" width="50%"/></imageobject>
     <textobject><phrase>Bad Focus Curve</phrase></textobject></mediaobject></screenshot>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-backlash">
+  <sect2 id="focus-backlash">
     <title>Focuser Backlash</title>
 
     <para>Backlash in the focuser setup is due to a combination of backlash in the electronic focuser itself (e.g. in the gearing
@@ -2067,9 +2067,9 @@
       </listitem>
     </itemizedlist>
     </para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-adaptive">
+  <sect2 id="focus-adaptive">
     <title>Adaptive Focus</title>
 
     <screenshot>
@@ -2196,10 +2196,10 @@
     the message box.</para>
 
     <para> The Adaptive Focus concept has been built into the <link linkend="build-filter-offsets">Build Offsets</link> tool.</para>
-  </sect3>
+  </sect2>
 
 
-  <sect3 id="Coefficient_of_Determination">
+  <sect2 id="Coefficient_of_Determination">
     <title>Coefficient of Determination, R²</title>
 
     <para> The Coefficient of Determination, or R², is calculated in order to
@@ -2228,9 +2228,9 @@
     forever.</para>
 
     <para> This feature is turned off by setting the R² Limit to 0.</para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="Levenberg-Marquardt">
+  <sect2 id="Levenberg-Marquardt">
     <title>Levenberg–Marquardt Solver</title>
 
     <para> The Levenberg-Marquardt (LM) algorithm is used to solve non-linear
@@ -2289,9 +2289,9 @@
 
     <para> Currently the solver is used to fit either a parabolic or a
     hyperbolic curve.</para>
-  </sect3>
+  </sect2>
 
-  <sect3 id="focus-aberration-inspector">
+  <sect2 id="focus-aberration-inspector">
     <title>Aberration Inspector</title>
 
     <screenshot>
@@ -2408,7 +2408,7 @@
 
     <para>The following sections describe the sections of the Aberration Inspector dialog.</para>
 
-    <sect4 id="aberration-inspector-vcurve">
+    <sect3 id="aberration-inspector-vcurve">
       <title>Aberration Inspector V-Curve</title>
 
       <screenshot>
@@ -2465,9 +2465,9 @@
     and 2 character identifier as displayed in the legend.</para>
 
     <para>Hover the mouse over a curve minimum to see more information about that curve.</para>
-    </sect4>
+    </sect3>
 
-    <sect4 id="aberration-inspector-table">
+    <sect3 id="aberration-inspector-table">
     <title>Aberration Inspector Table</title>
 
     <screenshot>
@@ -2540,9 +2540,9 @@
 
     <para>The recommended approach is to check the table for quality data and once achieved, move onto
     analysing the <link linkend="aberration-inspector-results">Aberration Inspector Results</link>.</para>
-    </sect4>
+    </sect3>
 
-    <sect4 id="aberration-inspector-results">
+    <sect3 id="aberration-inspector-results">
     <title>Aberration Inspector Results</title>
 
     <screenshot>
@@ -2602,9 +2602,9 @@
     <para>Because of the nature of the backfocus delta and tilt calculations, one will affect the other so it will
     probably be better to try and adjust both together, in small increments, rather than trying to perfect one in
     isolation, before adjusting the other.</para>
-    </sect4>
+    </sect3>
 
-    <sect4 id="aberration-inspector-3dgraphic">
+    <sect3 id="aberration-inspector-3dgraphic">
     <title>Aberration Inspector 3D Graphic</title>
 
     <screenshot>
@@ -2688,6 +2688,6 @@
     <link linkend="aberration-inspector-table">Table</link> and <link linkend="aberration-inspector-results">Results</link>
     sections of the dialog. Its purpose is to aid the user in understanding Aberration Inspector and to orient themselves
     with the information the tool provides.</para>
-    </sect4>
-  </sect3>
-</sect2>
+    </sect3>
+  </sect2>
+</sect1>
diff --git a/doc/ekos-guide.docbook b/doc/ekos-guide.docbook
index 6bca4abaf1..7ca6d5e123 100644
--- a/doc/ekos-guide.docbook
+++ b/doc/ekos-guide.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-guide">
+<sect1 id="ekos-guide">
     <title>Guide</title>
     <indexterm>
         <primary>Tools</primary>
@@ -18,14 +18,14 @@
             </textobject>
         </mediaobject>
     </screenshot>
-    <sect3 id="guide-Introduction">
+    <sect2 id="guide-Introduction">
         <title>Introduction</title>
         <para>
             The Ekos Guide Module performs autoguiding using either the powerful built-in guider, or at your option, external guiding via <ulink url="https://openphdguiding.org/">PHD2</ulink> or <ulink url="https://sourceforge.net/projects/linguider/">lin_guider</ulink>. Using the internal guiding, guider camera frames are captured and sent to Ekos for analysis. Depending on the deviations of the stars from their lock positions, guiding pulses corrections are sent to your mount's RA and DEC axes motors. Most of the &GUI; options in the Guide Module are well documented so just hover your mouse over an item and a tooltip will popup with helpful information.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="guide-Setup">
+    <sect2 id="guide-Setup">
         <title>Setup</title>
         <screenshot>
             <screeninfo>
@@ -99,8 +99,8 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
-    <sect3 id="guide-calibration">
+    </sect2>
+    <sect2 id="guide-calibration">
         <title>Calibration</title>
 
         <screenshot>
@@ -153,7 +153,7 @@
         <para>
             Ekos begins the calibration process by sending pulses to move the mount in RA and DEC. It pulses out the RA axis, then pulses it back in. After that it moves a little in DEC to clear and backlash that might exist, and then pulses out and back in for DEC. To view this graphically, click on the "Calibration Plot" subtab on the main guiding page.
         </para>
-        <sect4 id="guide-calibration-failures">
+        <sect3 id="guide-calibration-failures">
         <title>Calibration Failures</title>
             <para>
                 Calibration can fail for a variety of reasons. To improve the chances of success, try the tips below.
@@ -195,9 +195,9 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect4>
     </sect3>
-    <sect3 id="guide-guiding">
+    </sect2>
+    <sect2 id="guide-guiding">
         <title>Guiding</title>
 
         <screenshot>
@@ -239,8 +239,8 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
-    <sect3 id="guide-dithering">
+    </sect2>
+    <sect2 id="guide-dithering">
         <title>Dithering</title>
 
         <screenshot>
@@ -268,8 +268,8 @@
         <para>
             Non-guide dithering is also supported. This is useful when no guide camera is available or when performing short exposures. In this case, the mount can be commanded to dither in a random direction for up to the pulse specified in the <guilabel>Non-Guide Dither Pulse</guilabel> option.
         </para>
-    </sect3>
-    <sect3 id="guide-drift-graphics">
+    </sect2>
+    <sect2 id="guide-drift-graphics">
         <title>Drift Graphics</title>
         <screenshot>
             <screeninfo>
@@ -295,16 +295,16 @@
         <para>
             The colors of each axis can be customized in <link linkend="colors">&kstars; Settings color scheme</link>.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="guide-drift-plot">
+    <sect2 id="guide-drift-plot">
         <title>Drift Plot</title>
         <para>
             A bulls-eye scatter plot can be used to gauge the <emphasis>accuracy</emphasis> of the overall guiding performance. It is composed of three concentric rings of varying radii with the central green ring having a default radius of 2 arcsecs. The last RMS value is plotted as <inlinemediaobject><imageobject><imagedata fileref="add-circle.png" format="PNG"/></imageobject></inlinemediaobject> with its color reflecting which concentric ring it falls within. You can change the radius of the innermost green circle by adjusting the drift plot accuracy.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="guide-gpg">
+    <sect2 id="guide-gpg">
         <title>Guiding with GPG</title>
         <screenshot>
             <screeninfo>
@@ -325,8 +325,8 @@
         <para>
           The main settings to consider are Major Period and Estimate Period. If you know the worm period for your mount, perhaps by examining <ulink url="https://github.com/OpenPHDGuiding/phd2/wiki/Mount-Worm-Period-Info">this table</ulink>, then uncheck Estimate Period and enter your known Major Period. If not, then check Estimate Period.  Intra-frame dark guiding can be used to "spread out the GPG prediction. For instance, if you guide at 5s, you can set the dark guiding interval to 1s and its prediction is pulsed every second, but the guiding drift correction would be sent every 5s. In this way, it outputs the predicted corrections much faster than the guide camera exposure rate, effectively performing periodic error correction and allowing longer guide camera exposures. All the other parameters are best left to defaults.
         </para>
-    </sect3>
-    <sect3 id="guide-dark-frames">
+    </sect2>
+    <sect2 id="guide-dark-frames">
         <title>Dark Frames</title>
         <para>
             Dark frames can be helpful to reduce noise in your guide frames. If you choose to use this option, then it is recommended that you take dark frames before you begin your calibration or guiding procedure. To take a dark frame, check the <guilabel>Dark</guilabel> checkbox and then click <guibutton>Capture</guibutton>. For the first time this is performed, Ekos will ask you about your camera shutter. If your camera does not have a shutter, then Ekos will warn you anytime you take a dark frame to cover your camera/telescope before proceeding with the capture. On the other hand, if the camera already includes a shutter, then Ekos will directly proceed with taking the dark frame. All dark frames are automatically saved to Ekos Dark Frame Library. By default, the Dark Library keeps reusing dark frames for 30 days after which it will capture new dark frames. This value is configurable and can be adjusted in <link linkend="ekos">Ekos settings</link> in the &kstars; settings dialog.
@@ -347,9 +347,9 @@
         <para>
             It is recommended to take dark frames covering several binning and exposure values so that they may be reused transparently by Ekos whenever needed.
         </para>
-    </sect3>
+    </sect2>
     
-    <sect3 id="guide-phd2-support">
+    <sect2 id="guide-phd2-support">
         <title>PHD2 Support</title>
         <para>
             You can opt to select external PHD2 application to perform guiding instead of the built-in guider.
@@ -374,11 +374,11 @@
         <para>
             After launching PHD2, select your INDI equipment and set their options. From Ekos, connect to PHD2 by clicking the <guibutton>Connect</guibutton> button. On startup, Ekos will attempt to automatically connect to PHD2. Once the connection is established, you may begin the guiding immediately by click on the <guibutton>Guide</guibutton> button. PHD2 performs calibration if necessary. If dithering is selected, PHD2 is commanded to dither given the offset pixels indicated, and once guiding is settled and stable, the capture process in Ekos resumes.
         </para>
-    </sect3>
-    <sect3 id="guide-logs">
+    </sect2>
+    <sect2 id="guide-logs">
         <title>Guiding Logs</title>
         <para>
             Ekos' internal guider saves a CSV guide log in PHD2 format data that can be useful for analysis of the mount's performance. In Linux this is stored under <filename>~/.local/share/kstars/guidelogs/</filename>. This log is only available when using Ekos' internal guider. It should be compatible with <ulink url="https://openphdguiding.org/phd2-log-viewer/">PHD2's guide log viewer</ulink>.
         </para>
-    </sect3>
-</sect2>
+    </sect2>
+</sect1>
diff --git a/doc/ekos-logs.docbook b/doc/ekos-logs.docbook
index aa274d6a91..bd0bffa568 100644
--- a/doc/ekos-logs.docbook
+++ b/doc/ekos-logs.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-logs">
+<sect1 id="ekos-logs">
     <title>Logs</title>
     <indexterm>
         <primary>Tools</primary>
@@ -21,4 +21,4 @@
             </para>
         </caption>
     </mediaobject>
-</sect2>
+</sect1>
diff --git a/doc/ekos-profile-editor.docbook b/doc/ekos-profile-editor.docbook
index abc455b2f6..a085abc4da 100644
--- a/doc/ekos-profile-editor.docbook
+++ b/doc/ekos-profile-editor.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-profile-editor">
+<sect1 id="ekos-profile-editor">
     <title>Profile Editor</title>
     <indexterm>
         <primary>Tools</primary>
@@ -102,4 +102,4 @@
             </listitem>
         </varlistentry>
     </variablelist>    
-</sect2>
+</sect1>
diff --git a/doc/ekos-profile-wizard.docbook b/doc/ekos-profile-wizard.docbook
index 05ca966ba3..789acf6d4c 100644
--- a/doc/ekos-profile-wizard.docbook
+++ b/doc/ekos-profile-wizard.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-profile-wizard">
+<sect1 id="ekos-profile-wizard">
     <title>Profile Wizard</title>
     <indexterm>
         <primary>Tools</primary>
@@ -120,4 +120,4 @@
 <para>
     In the example above, we select Remote Astrometry, WatchDog, and SkySafari drivers. The detailed explanations for each is provided in the tooltip when you over them. Once done, click <guibutton>Create Profile</guibutton> button. You should now be presented with the Profile Editor.
 </para>
-</sect2>
+</sect1>
diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook
index a99c1b2710..61103b5cc0 100644
--- a/doc/ekos-scheduler.docbook
+++ b/doc/ekos-scheduler.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-scheduler">
+<sect1 id="ekos-scheduler">
     <title>Scheduler</title>
     <indexterm>
         <primary>Tools</primary>
@@ -18,13 +18,13 @@
             </textobject>
         </mediaobject>
     </screenshot>
-    <sect3 id="ekos-scheduler-introduction">
+    <sect2 id="ekos-scheduler-introduction">
       <title>Introduction</title>
         <para>
           The Ekos Scheduler is an important component of your imaging workflow. It connects to INDI, starts and stops all the other Ekos modules, schedules jobs according to their constraints and priorities, monitors those jobs as they execute, and then safely brings down the system when jobs are done, or before dawn. Whether you are running multi-day imaging sessions for multiple targets, or simply trying to image a single target for a few hours, it is advisable to have the Scheduler control your imaging sessions.
         </para>
-    </sect3>
-    <sect3 id="scheduler-table">
+    </sect2>
+    <sect2 id="scheduler-table">
         <title>Scheduler Table</title>
         <para>
           The heart of the Scheduler is a table displaying the list of Scheduler jobs the user wants to run. Associated with each jobs are attributes (mostly described in the settings section below). The attributes describe the name of the job, where the telescope should be pointed when imaging that job, a description of what types of images should be captured, constraints about when the jobs should run (⪚ altitude, twilight, moon, landscape blockages, &etc;), things that need to be done before and after the job is run, and strategies for dealing with errors.
@@ -57,8 +57,8 @@
             </listitem>
         </itemizedlist>
 
-    </sect3>
-    <sect3 id="scheduling-algorithm">
+    </sect2>
+    <sect2 id="scheduling-algorithm">
         <title>Scheduling Algorithm</title>
         <para>
           The Scheduler table (above) lists jobs in order of priority, with higher jobs (on lower-numbered rows) having higher priority than jobs further down the list (with higher-numbered rows). 
@@ -78,14 +78,14 @@
         <para>
           There is a checkbox option in the scheduler options menu called <guilabel>Use greedy scheduling</guilabel> which defaults to being checked.  The system works as described above when it is checked. When it is unchecked the scheduler is prevented from scheduling lower priority jobs when uncompleted higher priority jobs cannot run. This results in less efficient use of the system, but may give you more control over scheduling.
         </para>
-    </sect3>
-    <sect3 id="scheduler-files">
+    </sect2>
+    <sect2 id="scheduler-files">
         <title>Scheduler Files (.esq)</title>
         <para>
           The scheduler table with its list of jobs and attributes can be saved onto disk and read back in. It writes an .esq file. Controls for writing the current Scheduler table to disk, and reading back other .esq files are located above the table to the right.
         </para>
-    </sect3>
-    <sect3 id="ekos-scheduler-settings">
+    </sect2>
+    <sect2 id="ekos-scheduler-settings">
       <title>Settings</title>
         <para>
             Ekos Scheduler provides a simple interface to aid the user in setting the conditions and constraints required for an Scheduler job. You must select the <guilabel>Target</guilabel>, its coordinates, and the <guilabel>Sequence</guilabel> before you can add a job to the Scheduler.
@@ -140,8 +140,8 @@
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
-    <sect3 id="other-options">
+    </sect2>
+    <sect2 id="other-options">
         <title>Other options</title>
         <para>
           There are several other options to control how the Scheduler behaves. These are found in the general KStars Settings menu, shown below, in its Ekos tab and Scheduler sub-tab.
@@ -159,7 +159,7 @@
                 </textobject>
             </mediaobject>
         </screenshot>
-       <sect4 id="remember-job-progress">
+       <sect3 id="remember-job-progress">
         <title>Remember job progress</title>
         <para>
           Among the settings shown above, one important one is known as <guilabel>Remember job progress</guilabel>.  When this box is checked and a job is running, the Scheduler looks at the job's images already captured on disk, and doesn't re-capture the ones that are already there.  The benefit is that if a job is restarted, or re-run another night, or if multiple jobs are being run together, stopping and starting when they are runnable, then jobs re-start right where they left off. This works well with the <guilabel>Repeat until terminated</guilabel> job-completion option. If <guilabel>Remember job progress</guilabel> is unchecked, jobs would restart from the start of their sequence specification each time, which probably isn't what you want.  Unfortunately, if the images are not stored on the same computer that Ekos is running on, then this feature doesn't work and the jobs restart from their beginning.
@@ -167,8 +167,8 @@
         <para>
 A possibly confusing side-effect of <guilabel>Remember job progress</guilabel> is that if you've run a job using the (default) Sequence Completion finish condition, and it has captured all its images, and now you want to run the job again, the Scheduler won't schedule the job because it believes that all the images have already been captured. You'd either need to move those images elsewhere on disk, or change the finish condition to Repeat for N Times, or Repeat Until Terminated.
         </para>
-       </sect4>
-       <sect4 id="group-repeats">
+       </sect3>
+       <sect3 id="group-repeats">
         <title>Group repeats</title>
         <para>
           This feature allows you to run two or more scheduler jobs at roughly the same priority, such that if they were both runnable, they would progress at roughly the same rate.  This may be applicable, for example, to jobs imaging the multiple tiles in a mosaic, but is generally applicable to any set of jobs.
@@ -181,15 +181,15 @@ A possibly confusing side-effect of <guilabel>Remember job progress</guilabel> i
         <para>
 Practically speaking, imagine you had a 6-panel mosaic you wanted to alternate.  You might give all of those jobs the same group name, make them all ⪚ "Repeat for 5 times". Then, they would run in lock-step. The cadence of job switching would be controlled by the length of the sequence file assigned to each of those jobs. You wouldn't want to make the cadence too short (⪚ capturing one 2-minute image), as there is overhead in switching jobs. For instance, starting jobs may involved aligning, starting guiding, and even focusing.          
         </para>
-       </sect4>
-       <sect4 id="repeat-all-jobs">
+       </sect3>
+       <sect3 id="repeat-all-jobs">
         <title>Repeat all jobs</title>
         <para>
 There is a checkbox and number input right below the Scheduler jobs table that allows you to repeat the entire schedule N times.  This can be used to alternate a few jobs. You can just list the jobs on the scheduler, set it to repeat N times, and the jobs will repeat. However, this change is incompatible with 'Remember job progress (above) and unavailable if Remember Job Progress is checked. (Note: Remember Job Progress is recommended.)
         </para>
-       </sect4>
-    </sect3>
-    <sect3 id="workflow">
+       </sect3>
+    </sect2>
+    <sect2 id="workflow">
         <title>Workflow</title>
 
       <screenshot>
@@ -225,9 +225,9 @@ There is a checkbox and number input right below the Scheduler jobs table that a
                 </para>
             </listitem>
         </orderedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-startup-procedure">
+    <sect2 id="ekos-scheduler-startup-procedure">
         <title>Startup Procedure</title>
         <para>
             Startup procedure is unique to each observatory but may include:
@@ -277,9 +277,9 @@ There is a checkbox and number input right below the Scheduler jobs table that a
         <para>
             Ekos Scheduler only initiates the startup procedure once the startup time for the first Scheduler job is close (default <emphasis>lead</emphasis> time is 5 minutes before <emphasis>startup</emphasis> time). Once the startup procedure is completed successfully, the scheduler picks the Scheduler job target and starts the sequence process. If a startup script is specified, it shall be executed first.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-data-acquisition">
+    <sect2 id="ekos-scheduler-data-acquisition">
         <title>Data Acquisition</title>
         <para>
             Depending the on the user selection, the typical workflow proceeds as follows:
@@ -326,9 +326,9 @@ There is a checkbox and number input right below the Scheduler jobs table that a
                 </para>
             </listitem>
         </itemizedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-shutdown">
+    <sect2 id="ekos-scheduler-shutdown">
         <title>Shutdown</title>
         <para>
             Once the Scheduler job is completed successfully, the scheduler selects the next Scheduler job. If no job can be scheduled at this time, the mount is parked until a next job can run. Furthermore, if the next job is not due for a user-configurable time limit, the scheduler performs a <emphasis>preemptive</emphasis> shutdown to preserve resources and performs the startup procedure again when the target is due.
@@ -349,9 +349,9 @@ There is a checkbox and number input right below the Scheduler jobs table that a
                 </para>
             </caption>
         </mediaobject>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-weather-monitoring">
+    <sect2 id="ekos-scheduler-weather-monitoring">
         <title>Weather Monitoring</title>
         <para>
             Another critical feature of any remotely operated robotic observatory is weather monitoring. For weather updates, Ekos relies on the selected INDI weather driver to continuously monitor the weather conditions. For simplicity sake, the weather conditions can be summed in three states:
@@ -373,9 +373,9 @@ There is a checkbox and number input right below the Scheduler jobs table that a
                 </para>
             </listitem>
         </orderedlist>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-startup-and-shutdown-scripts">
+    <sect2 id="ekos-scheduler-startup-and-shutdown-scripts">
         <title>Startup & Shutdown Scripts</title>
         <para>
             Due to the uniqueness of each observatory, Ekos enables the user to select startup and shutdown scripts. The scripts take care of any necessary procedures that must take place on startup and shutdown stages. On startup, Ekos executes the startup scripts and only proceeds to the remainder of the startup procedure (unpark dome/unpark mount) if the script completes successfully. Conversely, the shutdown procedure begins with parking the mount & dome before executing the shutdown script as the final procedure.
@@ -409,9 +409,9 @@ exit(0)
         <para>
             The startup and shutdown scripts must be <emphasis>executable</emphasis> in order for Ekos to invoke them (⪚ use <userinput>chmod +x startup_script.py</userinput> to mark the script as executable). Ekos Scheduler enables truly simple robotic operation without the need of any human intervention in any step of the process. Without human presence, it becomes increasingly critical to gracefully recover from failures in any stage of the observation run. Using &plasma; notifications, the user can configure audible alarms and email notifications for the various events in the Scheduler.
         </para>
-    </sect3>
+    </sect2>
 
-    <sect3 id="ekos-scheduler-mosaic-Planner">
+    <sect2 id="ekos-scheduler-mosaic-Planner">
         <title>Mosaic Planner</title>
         <screenshot>
             <screeninfo>
@@ -549,5 +549,5 @@ exit(0)
         <para>
             Click <guibutton>Create Jobs</guibutton> to generate mosaic scheduler jobs and add them to the schedule queue. You can further edit the jobs individually, as you would normal Scheduler jobs.
         </para>
-    </sect3>
-</sect2>
+    </sect2>
+</sect1>
diff --git a/doc/ekos-setup.docbook b/doc/ekos-setup.docbook
index 12a591d811..63b43aadff 100644
--- a/doc/ekos-setup.docbook
+++ b/doc/ekos-setup.docbook
@@ -1,4 +1,4 @@
-<sect2 id="ekos-setup">
+<sect1 id="ekos-setup">
     <title>Ekos Setup</title>
 <indexterm>
     <primary>Tools</primary>
@@ -37,4 +37,4 @@
         </textobject>
     </mediaobject>
 </screenshot>
-</sect2>
+</sect1>
diff --git a/doc/ekos-tutorials.docbook b/doc/ekos-tutorials.docbook
index d11483b9db..eb987636fc 100644
--- a/doc/ekos-tutorials.docbook
+++ b/doc/ekos-tutorials.docbook
@@ -1,11 +1,11 @@
-<sect2 id="ekos-tutorials">
+<sect1 id="ekos-tutorials">
     <title>Ekos Tutorials</title>
 <indexterm>
     <primary>Tools</primary>
     <secondary>Ekos</secondary>
     <tertiary>Tutorials</tertiary>
 </indexterm>
-<sect3 id="ekos-tutorials-viewer">
+<sect2 id="ekos-tutorials-viewer">
     <title>Viewer</title>
     <para>
         StellarMate is shipped with a VNC Server. This enables you to access the whole StellarMate desktop remotely. To connect to VNC, you can either use a Desktop/Mobile VNC Client, or simply via any browser.
@@ -22,5 +22,5 @@
     <para>
         Once you access StellarMate, you can use it like any full-fledged computer. The default username is <userinput>stellarmate</userinput> and the default password is <userinput>smate</userinput>.
     </para>
-</sect3>
 </sect2>
+</sect1>
diff --git a/doc/ekos-user-interface.docbook b/doc/ekos-user-interface.docbook
index 14f24ff2a5..37ac6f31eb 100644
--- a/doc/ekos-user-interface.docbook
+++ b/doc/ekos-user-interface.docbook
@@ -1,4 +1,4 @@
-<sect2>
+<sect1>
     <title>User Interface</title>
     <indexterm>
         <primary>Tools</primary>
@@ -116,4 +116,4 @@
             </listitem>
         </varlistentry>
     </variablelist>
-</sect2>
+</sect1>
diff --git a/doc/ekos.docbook b/doc/ekos.docbook
index d1ab9d1347..89a2eeecf7 100644
--- a/doc/ekos.docbook
+++ b/doc/ekos.docbook
@@ -1,8 +1,6 @@
-<sect1 id="tool-ekos">
+<chapter id="ekos">
 <title>Ekos</title>
-<indexterm><primary>Tools</primary>
-<secondary>Ekos</secondary>
-</indexterm>
+<indexterm><primary>Ekos</primary></indexterm>
 
 <para>
     <emphasis role="bold">Ekos</emphasis> is an advanced cross-platform (&Windows;, &MacOS;, &Linux;) observatory control and automation tool with a particular focus on Astrophotography. It is based on a modular extensible framework to perform common astrophotography tasks. This includes highly accurate GOTOs using astrometry solver, ability to measure <emphasis>and</emphasis> correct polar alignment errors, auto-focus & auto-guide capabilities, and capture of single or stack of images with filter wheel support. Ekos is shipped with &kstars;.
@@ -140,4 +138,4 @@
 &tool-ekos-analyze;
 &tool-ekos-tutorials;
 
-</sect1>
+</chapter>
diff --git a/doc/fitsviewer.docbook b/doc/fitsviewer.docbook
index c7ae421ef4..480d15418d 100644
--- a/doc/fitsviewer.docbook
+++ b/doc/fitsviewer.docbook
@@ -1,8 +1,6 @@
-<sect1 id="tool-fitsviewer">
-<title><acronym>FITS</acronym> Viewer Tool</title>
-<indexterm><primary>Tools</primary>
-<secondary>FITS Viewer</secondary>
-</indexterm>
+<chapter id="fitsviewer">
+<title><acronym>FITS</acronym> Viewer</title>
+<indexterm><primary>FITS Viewer</primary></indexterm>
 
 <para>FITS, or Flexible Image Transport System, is the standard format for representing images and data in Astronomy.  The &kstars; FITS Viewer is a tool to view those images. It is not designed for editing of FITS Images.</para>
 
@@ -12,13 +10,13 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
 <keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>.</para>
 
 <screenshot>
-  <screeninfo>The FITS Viewer Tool</screeninfo>
+  <screeninfo>The FITS Viewer</screeninfo>
   <mediaobject>
     <imageobject>
       <imagedata fileref="fitsviewer1.png" format="PNG"/>
     </imageobject>
     <textobject>
-      <phrase>FITS Viewer Tool</phrase>
+      <phrase>FITS Viewer</phrase>
     </textobject>
   </mediaobject>
 </screenshot>
@@ -26,18 +24,18 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
 <para>The above diagram illustrates the FITS Viewer main work area and window. There is also a hidden area that can be exposed by moving the mouse over the 6 small dots on the left side (about center of the image vertically) and pressing and holding the mouse, sliding it over to the right a bit.</para>
 
 <screenshot>
-  <screeninfo>The FITS Viewer Tool with sliding panel open</screeninfo>
+  <screeninfo>The FITS Viewer with sliding panel open</screeninfo>
   <mediaobject>
     <imageobject>
       <imagedata fileref="fitsviewer2.png" format="PNG"/>
     </imageobject>
     <textobject>
-      <phrase>FITS Viewer Tool with sliding panel open</phrase>
+      <phrase>FITS Viewer with sliding panel open</phrase>
     </textobject>
   </mediaobject>
 </screenshot>
 
-<sect2 id="fits-viewer-main-controls">
+<sect1 id="fits-viewer-main-controls">
     <title>Main Controls</title>
 
 <para>The various controls and displays for the FITS Viewer are shown below. The tool provides basic functions for image display.  While the tool adhere to the FITS standard, it does not support all possible FITS features:</para>
@@ -231,8 +229,8 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
 <para>
     Hovering over any option shall display a detailed tooltip that explains its function.
 </para>
-</sect2>
-<sect2 id="fits-viewer-features">
+</sect1>
+<sect1 id="fits-viewer-features">
     <title>Features</title>
     <variablelist>
         <varlistentry>
@@ -273,9 +271,9 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
             </listitem>
         </varlistentry>
     </variablelist>
-</sect2>
+</sect1>
 
-<sect2 id="fits-viewer-solver">
+<sect1 id="fits-viewer-solver">
     <title>FITS Viewer Solver</title>
     <screenshot>
         <screeninfo>
@@ -332,9 +330,9 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
             <para>
               To inspect or modify the profile, the user would open the align tab in Ekos, go to the Options menu, select the StellarSolver Options tab, make sure the right Options profile is selected, and click the pencil to view or edit that profile.
               </para>
-</sect2>
+</sect1>
 
-<sect2 id="fits-viewer-embedded">
+<sect1 id="fits-viewer-embedded">
     <title>Embedded FITS Viewer</title>
     <screenshot>
         <screeninfo>
@@ -395,11 +393,11 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
         </listitem>
     </itemizedlist>
     <para>
-        The floating bar is automatically hidden once the mouse leaves the embedded viewer area. You can use the mouse to pan and zoom just like the standalone FITS Viewer tool. The green tracking box can be used to select a specific star or region within the image, for example, to select a guide star.
+        The floating bar is automatically hidden once the mouse leaves the embedded viewer area. You can use the mouse to pan and zoom just like the standalone FITS Viewer. The green tracking box can be used to select a specific star or region within the image, for example, to select a guide star.
     </para>
-</sect2>
+</sect1>
 
-<sect2 id="fits-viewer-3d-star-profile">
+<sect1 id="fits-viewer-3d-star-profile">
 <title>3D Star Profile & Data Visualization Tool</title>
 <screenshot>
         <screeninfo>
@@ -494,5 +492,5 @@ To open a FITS file, select the <menuchoice><guimenu>File</guimenu>
             </textobject>
         </mediaobject>
     </screenshot>
-</sect2>
 </sect1>
+</chapter>
diff --git a/doc/index.docbook b/doc/index.docbook
index 5e535006b7..3065056719 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -56,10 +56,9 @@
   <!ENTITY tool-altvstime SYSTEM "altvstime.docbook">
   <!ENTITY tool-calculator SYSTEM "calculator.docbook">
   <!ENTITY tool-details SYSTEM "details.docbook">
-  <!ENTITY tool-ekos SYSTEM "ekos.docbook">
+  <!ENTITY ekos SYSTEM "ekos.docbook">
   <!ENTITY tool-ekos-align SYSTEM "ekos-align.docbook">
   <!ENTITY tool-ekos-capture SYSTEM "ekos-capture.docbook">
-  <!ENTITY tool-ekos-fits-viewer SYSTEM "ekos-fits-viewer.docbook">
   <!ENTITY tool-ekos-focus SYSTEM "ekos-focus.docbook">
   <!ENTITY tool-ekos-guide SYSTEM "ekos-guide.docbook">
   <!ENTITY tool-ekos-logs SYSTEM "ekos-logs.docbook">
@@ -71,7 +70,7 @@
   <!ENTITY tool-ekos-tutorials SYSTEM "ekos-tutorials.docbook">
   <!ENTITY tool-ekos-user-interface SYSTEM "ekos-user-interface.docbook">
   <!ENTITY tool-eyepieceview SYSTEM "eyepieceview.docbook">
-  <!ENTITY tool-fitsviewer SYSTEM "fitsviewer.docbook">
+  <!ENTITY fitsviewer SYSTEM "fitsviewer.docbook">
   <!ENTITY tool-jmoons SYSTEM "jmoons.docbook">
   <!ENTITY tool-obsplanner SYSTEM "obsplanner.docbook">
   <!ENTITY tool-scriptbuilder SYSTEM "scriptbuilder.docbook">
@@ -89,13 +88,6 @@
 <bookinfo>
 
 <authorgroup>
-<author>
-<firstname>Jason</firstname>
-<surname>Harris</surname>
-<affiliation>
-<address>&Jason.Harris.mail;</address>
-</affiliation>
-</author>
 
 <othercredit role="developer">
 <firstname>Jasem</firstname>
@@ -106,6 +98,15 @@
 <contrib>Lead Developer & Maintainer</contrib>
 </othercredit>
 
+<othercredit role="developer">
+<firstname>Jason</firstname>
+<surname>Harris</surname>
+<affiliation>
+<address>&Jason.Harris.mail;</address>
+</affiliation>
+<contrib>Original Author</contrib>
+</othercredit>
+
 <othercredit role="developer">
 <firstname>Akarsh</firstname>
 <surname>Simha</surname>
@@ -230,17 +231,34 @@
 
 <abstract>
 <para>
-&kstars; is free, open source, cross-platform Astronomy Software.
-
-It provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. The display includes up to 100 million stars, 13,000 deep-sky objects,all 8 planets, the Sun and Moon, and thousands of comets, asteroids, supernovae, and satellites.
-
-For students and teachers, it supports adjustable simulation speeds in order to view phenomena that happen over long timescales, the &kstars; Astrocalculator to predict conjunctions, and many common astronomical calculations. For the amateur astronomer, it provides an observation planner, a sky calendar tool, and an FOV editor to calculate field of view of equipment and display them. Find out interesting objects in the <quote>What's up Tonight</quote> tool, plot altitude vs. time graphs for any object, print high-quality sky charts, and gain access to lots of information and resources to help you explore the universe!
-
-HiPS all-sky progressive overlay provide stunning views from numerous surveys spanning the whole electromagnetic spectrum.
-
-Included with &kstars; is Ekos astrophotography suite, a complete astrophotography solution that can control all INDI devices including numerous telescopes, CCDs, DSLRs, focusers, filters, and a lot more. Ekos supports highly accurate tracking using online and offline astrometry solver, autofocus and autoguiding capabilities, and capture of single or multiple images using the powerful built in sequence manager.
+&kstars; is free, open source, cross-platform astronomy software. It provides the &kstars; skymap, a digital planetarium with overlays and simulation tools, the Ekos astrophotography suite which acts as a client for INDI device drivers, and the FITS Viewer which displays captured sky images.
 </para>
+
+<itemizedlist>
+ <listitem>
+   <para>
+The &kstars; skymap provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. The display includes up to 100 million stars, 13,000 deep-sky objects, all 8 planets, the Sun and Moon, and thousands of comets, asteroids, supernovae, and satellites.
+   </para>
+   <para>
+For students and teachers, it supports adjustable simulation speeds in order to view phenomena that happen over long timescales, the &kstars; Astrocalculator to predict conjunctions, and many common astronomical calculations. For the amateur astronomer, it provides an observation planner, a sky calendar tool, and an FOV editor to calculate field of view of equipment and display them. Find out interesting objects in the <quote>What's up Tonight</quote> tool, plot altitude vs. time graphs for any object, print high-quality sky charts, and gain access to lots of information and resources to help you explore the universe!  The HiPS all-sky progressive overlay provide stunning views from numerous surveys spanning the whole electromagnetic spectrum.
+   </para>
+ </listitem>
+
+ <listitem>
+   <para>
+     Ekos is a complete astrophotography solution that provides everything needed for automated or manual deep-sky imaging.  It can control all INDI devices including numerous telescopes, CCD and CMOS astronomy cameras, DSLRs, focusers, filters, rotators, domes and a lot more. Ekos supports highly accurate tracking using online and offline astrometry solvers, autofocus and autoguiding capabilities, and capture of single or multiple images using its powerful built in scheduler.  It integrates well with the skymap, and FITS Viewer. It also has tools for polar alignment and measuing optical aberrations.
+  </para>
+ </listitem>
+
+ <listitem>
+   <para>
+     The FITS Viewer can display FITS and other format images, including those captured by Ekos. One can zoom and pan, view stretched versions of the images, see image histograms, plate-solve and find stars and coordinates in the images. 
+  </para>
+ </listitem>
+
+</itemizedlist>
 </abstract>
+   
 
 <keywordset>
 <keyword>KDE</keyword>
@@ -289,12 +307,12 @@ Enable <link linkend="hips">HiPS all-sky progressive overlay</link> to fetch hig
 This features requires a fast internet connection in order to download the images. The images are cached locally to reduce bandwidth. You can optimize the caching options to best balance between disk space versus bandwidth.
 </para>
 <para>
-However, &kstars; is not just for students.  You can control telescopes and cameras with &kstars;, using the elegant and powerful <link linkend="indi">INDI</link> protocol.  &kstars; supports several popular
-telescopes including Meade's LX200 family and Celestron GPS.  Several popular CCD cameras, webcams, and computerized focusers are also supported.  Simple slew/track commands are integrated directly into the main window's
+&kstars; is also for astrophotographers. You can control telescopes and cameras using the elegant and powerful <link linkend="indi">INDI</link> protocol. Ekos supports many popular telescopes including Meade's LX200 family and Celestron GPS.  Many popular CCD, CMOS and DSLR astrophotography cameras, webcams, and computerized focusers are also supported.  Simple slew/track commands are integrated directly into the skymap's
 popup menu, and the INDI Control Panel provides full access to all of your telescope's functions. INDI's Client/Server
 architecture allows for seamless control of any number of <link linkend="indi-kstars-setup">local</link> or <link linkend="indi-remote-control">remote</link> telescopes using a single
-&kstars; session. For advanced users, &kstars; provides Ekos, a complete astrophotography suite for Linux. <ulink url="https://indilib.org/about/ekos.html">Ekos</ulink> is based on a modular extensible framework to perform common astrophotography tasks. This includes highly accurate GOTOs using astrometry solver, ability to measure and correct polar alignment errors , auto-focus and auto-guide capabilities,
-and capture of single or stack of images with filter wheel support.
+&kstars; session. For advanced users, &kstars; provides Ekos, a complete astrophotography suite for Linux, Mac and Windows. <ulink url="https://indilib.org/about/ekos.html">Ekos</ulink> is based on a modular extensible framework to perform common astrophotography tasks. This includes highly accurate GOTOs using astrometry solver, ability to measure and correct polar alignment errors , auto-focus and auto-guide capabilities,
+and capture of single or stack of images with filter wheel, rotator and dome support. Complex jobs can be scheduled and run automatically with the Ekos scheduler, taking into account priority, altitude, terrain, moon and twilight constraints.
+You can view the progress of a night's astrophotography session using the Ekos Analyze module, and view the images captured using the FITS Viewer. Ekos is described in <link linkend="ekos">Chapter 5.</link>
 </para>
 <para>
 We are very interested in your feedback; please report bugs or feature requests to the &kstars; development mailing list: <email>kstars-devel AT kde.org</email>. You can also use the automated bug reporting tool, accessible from the Help menu.
@@ -308,6 +326,8 @@ We are very interested in your feedback; please report bugs or feature requests
 &quicktour;   <!--A Quick Tour of &kstars;-->
 &config;      <!--Configuring &kstars;-->
 &commands;    <!--Command Reference-->
+&ekos;        <!--Ekos-->
+&fitsviewer;        <!--FITS Viewer-->
 &tools;       <!--&kstars; Tools-->
 &dumpmode;    <!--Command-line image-dump mode-->
 &indi;        <!-- INDI-->
diff --git a/doc/indi.docbook b/doc/indi.docbook
index f690c2a71c..43cc3b1c5c 100644
--- a/doc/indi.docbook
+++ b/doc/indi.docbook
@@ -313,7 +313,7 @@ The device can be controlled fully from the <guimenuitem>INDI Control Panel...</
 </para>
 
 <para>The standard format for image capture is FITS. Once an image is captured and downloaded,
-it will be automatically displayed in the &kstars; <link linkend="tool-fitsviewer">FITS Viewer</link>.
+it will be automatically displayed in the &kstars; <link linkend="fitsviewer">FITS Viewer</link>.
 </para>
 </sect1>
 
diff --git a/doc/quicktour.docbook b/doc/quicktour.docbook
index 5d2a841c96..ffa2823985 100644
--- a/doc/quicktour.docbook
+++ b/doc/quicktour.docbook
@@ -1,8 +1,8 @@
 <chapter id="using-kstars">
-<title>A Quick Tour of &kstars;</title>
+<title>A Quick Tour of the &kstars; Skymap</title>
 
 <para>
-This chapter presents a guided tour of &kstars;, introducing
+This chapter presents a guided tour of the &kstars; skymap, introducing
 many of its important features.
 </para>
 
@@ -423,7 +423,7 @@ object.
 <sect1 id="endtour">
 <title>End of the Tour</title>
 <para>
-This concludes the tour of &kstars;, although we have only scratched
+This concludes the tour of the &kstars; skymap, although we have only scratched
 the surface of the available features.  &kstars; includes many useful
 <link linkend="tools">astronomy tools</link>, it can directly
 <link linkend="indi">control your telescope</link>, and it offers a
diff --git a/doc/tools.docbook b/doc/tools.docbook
index c472e5f7a8..3f32c731db 100644
--- a/doc/tools.docbook
+++ b/doc/tools.docbook
@@ -14,10 +14,8 @@ some more advanced aspects of astronomy and the night sky.
 <listitem><para><link linkend="tool-eyepieceview">Simulate Eyepiece View</link></para></listitem>
 <listitem><para><link linkend="tool-scriptbuilder">Script  Builder</link></para></listitem>
 <listitem><para><link linkend="tool-solarsys">Solar System Viewer</link></para></listitem>
-<listitem><para><link linkend="tool-ekos">Ekos</link></para></listitem>
 <listitem><para><link linkend="tool-jmoons">Jupiter Moons Tool</link></para></listitem>
 <listitem><para><link linkend="tool-obsplanner">Observation Planner</link></para></listitem>
-<listitem><para><link linkend="tool-fitsviewer">FITS Viewer</link></para></listitem>
 </itemizedlist>
 
 &tool-details;
@@ -27,9 +25,7 @@ some more advanced aspects of astronomy and the night sky.
 &tool-whatsup;
 &tool-scriptbuilder;
 &tool-solarsys;
-&tool-ekos;
 &tool-jmoons;
 &tool-obsplanner;
-&tool-fitsviewer;
 
 </chapter>


More information about the kde-doc-english mailing list