Git commit 41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd by Yuri Chornoivan. Committed on 02/12/2023 at 19:28. Pushed by yurchor into branch 'master'.
Fix minor typos M +1 -1 doc/commands.docbook M +2 -2 doc/ekos-capture.docbook M +1 -1 doc/ekos-focus.docbook M +1 -1 doc/timezones.docbook https://invent.kde.org/education/kstars/-/commit/41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd diff --git a/doc/commands.docbook b/doc/commands.docbook index 8560d8da73..721a4cef01 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 a image in the FITS Viewer tool. +<listitem><para>Open an image in the FITS Viewer tool. </para></listitem> </varlistentry> diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook index 80c67d6a10..6610f9cb33 100644 --- a/doc/ekos-capture.docbook +++ b/doc/ekos-capture.docbook @@ -646,7 +646,7 @@ The value of image stacking is that as images are stacked, the accumulation of e <listitem> <para> <guimenuitem>Table</guimenuitem>: A table provides details for stacking based upon the number of hours planned for imaging.</para> -<para>The table provides a quick reference for finding the approximate number of sub-exposures that might be completed for a given number of hours in a imaging session. But some functions that consume time are not included in this time calculation. For example, USB based cameras typically take some time for data transmission, or if the user has selected automatic dithering, additional time will be consumed in the imaging process, which is not included in this time calculation.</para> +<para>The table provides a quick reference for finding the approximate number of sub-exposures that might be completed for a given number of hours in an imaging session. But some functions that consume time are not included in this time calculation. For example, USB based cameras typically take some time for data transmission, or if the user has selected automatic dithering, additional time will be consumed in the imaging process, which is not included in this time calculation.</para> <para>The far right column of the table shows the calculated time/noise ratio of the integrated (stacked) image that would be produced.</para> </listitem> <listitem> @@ -669,7 +669,7 @@ Depending on the various inputs and imaging conditions, the potential quality of </para> <para> -Part of the value of using a Time/Noise ratio as the input for the calculation of the required number of sub-exposures is that it should tend to compensate for the differences in relative noise for sub-exposures of various lengths. A shorter sub-exposure would have a lower time/noise ratio, so it has less capacity to improve a integrated image. Therefore, a disproportionately higher number of short exposures are needed to achieve a given time/noise ratio in an integrated image.</para> +Part of the value of using a Time/Noise ratio as the input for the calculation of the required number of sub-exposures is that it should tend to compensate for the differences in relative noise for sub-exposures of various lengths. A shorter sub-exposure would have a lower time/noise ratio, so it has less capacity to improve an integrated image. Therefore, a disproportionately higher number of short exposures are needed to achieve a given time/noise ratio in an integrated image.</para> <para>As an example, consider the calculation of the number of sub-exposures required when two sub-exposures times were compared: a 300 second sub-exposure vs a 30 second sub-exposure. The 300 second sub-exposure had a calculated noise of 22.1, resulting in a sub-exposure time/noise ratio of 13.6. When the 'noise increase %' is raised to force the exposure time down to 30 seconds, we see a calculated noise of 9.47, resulting in a much lower sub-exposure time/noise ratio of 3.2. The 300 second exposure is of significantly higher potential quality than the 30 second exposure. We will demand the default time/noise ratio of 80 for integration in both of these cases.</para> diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 0e4292fd7f..10d53f6ef0 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -2400,7 +2400,7 @@ will vary by equipment and must be discovered by the user by trial and error. Always follow the recommendations of the tilt / backfocus device manufacturer.</para> - <para>Each time Aberration Inspector is run it lauches a new dialog with the run number appended to the title. + <para>Each time Aberration Inspector is run it launches a new dialog with the run number appended to the title. This way several runs can be performed and the results compared. Note, however, that the dialog holds a lot of data (roughly 10x the amount of a standard Autofocus run). The system resources associated with this are released when the dialog is closed. For this reason on lower powered machines, once the tool has been used, it is recommended diff --git a/doc/timezones.docbook b/doc/timezones.docbook index 6f20ef9db8..b426e42652 100644 --- a/doc/timezones.docbook +++ b/doc/timezones.docbook @@ -25,7 +25,7 @@ This localization of time is accomplished by dividing the globe into 24 vertical slices called <firstterm>Time Zones</firstterm>. The Local Time is the same within any given zone, but the time in each zone is one Hour <emphasis>earlier</emphasis> than the time in the neighboring Zone to the East. -Actually, this is a idealized simplification; real Time Zone boundaries are not +Actually, this is an idealized simplification; real Time Zone boundaries are not straight vertical lines, because they often follow national boundaries and other political considerations. </para><para>
