[education/kstars] /: Fix minor typos

[Yuri Chornoivan]

Git commit 8db413303fa620d4b67958a0b256d255bc6163e2 by Yuri Chornoivan.
Committed on 22/08/2024 at 12:58.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +4    -4    doc/ekos-extensions.docbook
M  +1    -1    kstars/ekos/manager.cpp

https://invent.kde.org/education/kstars/-/commit/8db413303fa620d4b67958a0b256d255bc6163e2

diff --git a/doc/ekos-extensions.docbook b/doc/ekos-extensions.docbook
index 07de3eb9c5..7541a05e26 100644
--- a/doc/ekos-extensions.docbook
+++ b/doc/ekos-extensions.docbook
@@ -35,7 +35,7 @@
             It is mandatory that the configuration file contains a line starting with <emphasis role="bold">minimum_kstars_version=n.n.n</emphasis> where n.n.n is the lowest version of KStars that supports the extension ⪚ 3.7.1
             </para>
             <para>
-            Optionally (and non-preferred) the configuration file may contain a line starting with <emphasis role="bold">runDetached=true</emphasis>. If present this line makes the extension run independently from KStars. Once it has been started the extension can not pass status information back to Ekos. This should only be used by extensions that are required to continue to run after KStars has closed. The extension must also provide it's own user interface.
+            Optionally (and non-preferred) the configuration file may contain a line starting with <emphasis role="bold">runDetached=true</emphasis>. If present this line makes the extension run independently from KStars. Once it has been started the extension can not pass status information back to Ekos. This should only be used by extensions that are required to continue to run after KStars has closed. The extension must also provide its own user interface.
             </para>
             <para>
             Additionally the configuration file can contain any other parameters that the extension author decides and free text.
@@ -43,7 +43,7 @@
           </listitem>
           <listitem>
             <para>
-            The icon file, if present, must be named the same as the extension executable with the addition of the appropriate file name extension for the image format, .jpg, .bmp, .gif, .png and .svg are supported. If provided this icon will be used in the extension selection ComboBox. If an icon is not provide a default icon will be used instead.
+            The icon file, if present, must be named the same as the extension executable with the addition of the appropriate file name extension for the image format, .jpg, .bmp, .gif, .png and .svg are supported. If provided this icon will be used in the extension selection ComboBox. If an icon is not provided a default icon will be used instead.
             </para>
           </listitem>
         </itemizedlist>
@@ -67,7 +67,7 @@
          </listitem>
          <listitem>
             <para>
-            Each extension must check for the existence and validity of it's own configuration file. The minimum_kstars_version configuration file entry must be checked against an internal reference to confirm that the configuration file matches the extension requirements. See the skeleton example.
+            Each extension must check for the existence and validity of its own configuration file. The minimum_kstars_version configuration file entry must be checked against an internal reference to confirm that the configuration file matches the extension requirements. See the skeleton example.
             </para>
           </listitem>
           <listitem>
@@ -77,7 +77,7 @@
           </listitem>
           <listitem>
             <para>
-              All interaction with KStars/Ekos/INDI should be via the DBus interface. See the skeleton example. Useful tools for interrogating, monitoring and understanding DBus include <ulink url="https://wiki.gnome.org/Apps/DFeet>D-Feet">D-Feet</ulink> and <ulink url="https://gitlab.freedesktop.org/bustle/bustle">Bustle</ulink>
+              All interaction with KStars/Ekos/INDI should be via the DBus interface. See the skeleton example. Useful tools for interrogating, monitoring and understanding DBus include <ulink url="https://wiki.gnome.org/Apps/DFeet>D-Feet</ulink> and <ulink url="https://gitlab.freedesktop.org/bustle/bustle">Bustle</ulink>
             </para>
             <para>
             It may appear on initial investigation that using the Qt DBus Adaptors system would be much easier than direct use of the Qt DBus Interfaces/Messages and KStars does provide the required xml definitions. However currently there is heavy use of custom types the definitions of which are combined with other information in the KStars sources. This results in a large set of files from KStars that require inclusion within an extension in order to make use of the Qt DBus Adaptors. Hopefully this will be addressed in the future.
diff --git a/kstars/ekos/manager.cpp b/kstars/ekos/manager.cpp
index 079f94f647..570949fb6b 100644
--- a/kstars/ekos/manager.cpp
+++ b/kstars/ekos/manager.cpp
@@ -425,7 +425,7 @@ Manager::Manager(QWidget * parent) : QDialog(parent)
                 extensionCombo->setEnabled(false);
             break;
             case EXTENSION_STOPPED:
-                appendLogText(i18n("Extension '%1 stopped", extensionCombo->currentText()));
+                appendLogText(i18n("Extension '%1' stopped", extensionCombo->currentText()));
                 extensionB->setIcon(QIcon::fromTheme("media-playback-start"));
                 extensionB->setEnabled(true);
                 extensionCombo->setEnabled(true);