diff --git a/Doc/Sdi/CloudProvider/gettingStarted.xml b/Doc/Sdi/CloudProvider/gettingStarted.xml
index f1058eb3eca8d65dc4d109a807992c0bda40390c..4348d4b20576214eb676976ee4d6eb7e8105f95b 100644
--- a/Doc/Sdi/CloudProvider/gettingStarted.xml
+++ b/Doc/Sdi/CloudProvider/gettingStarted.xml
@@ -292,17 +292,21 @@
 │                                                                                      │
 └──────────────────────────────────────────────────────────────────────────────────────┘</screen>
                   </listitem>
-                </itemizedlist>
 
-                <para>Upon finishing your choices enter <quote>reboot</quote>
-                and hit return. Log in again. Your keyboard should now work as
-                expected.</para>
+                  <listitem>
+                    <para>Restart keyboard service:</para>
+
+                    <screen>service keyboard-setup restart</screen>
+
+                    <para>Your keyboard should now work as expected.</para>
+                  </listitem>
+                </itemizedlist>
               </listitem>
 
               <listitem>
                 <para>ping your server and access it by <xref
                 linkend="glo_ssh"/> / password login rather than just using
-                the <orgname>Hetzner</orgname> GUI console. </para>
+                the <orgname>Hetzner</orgname> GUI console.</para>
               </listitem>
 
               <listitem>
@@ -312,7 +316,7 @@
 
               <listitem>
                 <para><emphasis role="red">Finally delete your server avoiding
-                10€ / Month being billed to our department!</emphasis></para>
+                10€ / month being billed to our department!</emphasis></para>
 
                 <para>(You may re-create it any time you like.)</para>
               </listitem>
@@ -322,6 +326,45 @@
       </qandadiv>
     </qandaset>
 
+    <figure xml:id="sdi_cloudProvider_minimalServerIssues">
+      <title>Current server security flaws</title>
+
+      <itemizedlist>
+        <listitem>
+          <para>No updates, just (likely) outdated installation image</para>
+        </listitem>
+
+        <listitem>
+          <para>Password based logins being notoriously prone to
+          attacks.</para>
+
+          <para>Solution: Use public/private key based <xref
+          linkend="glo_ssh"/> login.</para>
+        </listitem>
+
+        <listitem>
+          <para>There is no firewall yet restricting network access.
+          Insecurely configured supplementary software components
+          <abbrev>e.g.</abbrev> database servers may lead to disaster.</para>
+
+          <para>Two choices:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Cloud provider level <link
+              xlink:href="https://docs.hetzner.com/cloud/firewalls">centralized
+              firewall</link>.</para>
+            </listitem>
+
+            <listitem>
+              <para>Host local firewall, e.g. <productname
+              xlink:href="https://wiki.ubuntu.com/UncomplicatedFirewall">Ufw</productname>.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+      </itemizedlist>
+    </figure>
+
     <figure xml:id="sdi_cloudProvider_webAdminGui_createSshKeyPair">
       <title>Preliminary: Create an <command>ssh</command> key pair</title>
 
@@ -376,48 +419,9 @@ Your public key has been saved in /home/sdiuser/.ssh/id_ed25519.pub <co
       </calloutlist>
     </figure>
 
-    <figure xml:id="sdi_cloudProvider_minimalServerIssues">
-      <title>Current server security flaws</title>
-
-      <itemizedlist>
-        <listitem>
-          <para>No updates, just (likely) outdated installation image</para>
-        </listitem>
-
-        <listitem>
-          <para>Password based logins being notoriously prone to
-          attacks.</para>
-
-          <para>Solution: Use public/private key based <xref
-          linkend="glo_ssh"/> login.</para>
-        </listitem>
-
-        <listitem>
-          <para>There is no firewall yet restricting network access.
-          Insecurely configured supplementary software components
-          <abbrev>e.g.</abbrev> database servers may lead to disaster.</para>
-
-          <para>Two choices:</para>
-
-          <itemizedlist>
-            <listitem>
-              <para> Cloud provider level <link
-              xlink:href="https://docs.hetzner.com/cloud/firewalls">centralized
-              firewall</link>.</para>
-            </listitem>
-
-            <listitem>
-              <para>Host local firewall, e.g. <productname
-              xlink:href="https://wiki.ubuntu.com/UncomplicatedFirewall">Ufw</productname>.</para>
-            </listitem>
-          </itemizedlist>
-        </listitem>
-      </itemizedlist>
-    </figure>
-
     <qandaset defaultlabel="qanda"
               xml:id="sdi_cloudProvider_webAdminGui_quandaServerImproved">
-      <title>Improve your server!</title>
+      <title>Improve your server's security!</title>
 
       <qandadiv>
         <qandaentry>
@@ -553,7 +557,7 @@ Saving to: ‘STDOUT’
                 browser of choice.</para>
 
                 <para>Why does external access fail although local access
-                works? </para>
+                works?</para>
               </listitem>
 
               <listitem>
@@ -836,7 +840,8 @@ resource "hcloud_server" "helloServer" {
   ssh_keys     = [hcloud_ssh_key.<emphasis role="red">loginUser</emphasis>.id]
 }</programlisting>
 
-      <para>Note: Remove any conflicting manually installed keys
+      <para>Note: Use the <orgname>Hetzner</orgname> Web GUI for removing any
+      conflicting manually installed <xref linkend="glo_ssh"/> keys
       beforehand.</para>
     </figure>
 
@@ -1051,10 +1056,11 @@ provider "hcloud" {
 
               <listitem>
                 <para>Subject your configuration to version control in a
-                <productname>Git</productname> project. Versioning the
-                previous <xref linkend="glo_Terraform"/> configuration might
-                expose your cloud provider's API token. Circumvent this
-                problem by following the steps outlined in <xref
+                <productname>Git</productname> project. Putting the previous
+                <xref linkend="glo_Terraform"/> configuration under version
+                control might expose your cloud provider's API token.
+                Circumvent this problem by following the steps outlined in
+                <xref
                 linkend="sdi_cloudProvider_terra_hello_sshProblemApiTokenSolveFile"/>.</para>
               </listitem>