From 69cefd31ad6e82ad0d9ca52ca483288b57a5cf85 Mon Sep 17 00:00:00 2001
From: Dmitri Popov <dpopov@suse.de>
Date: Thu, 1 Feb 2024 14:30:31 +0100
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Daria Vladykina <daria.vladykina@suse.com>
---
 xml/art_minimal-vm.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/art_minimal-vm.xml b/xml/art_minimal-vm.xml
index 8268bdfe7b..58bc606a55 100644
--- a/xml/art_minimal-vm.xml
+++ b/xml/art_minimal-vm.xml
@@ -49,7 +49,7 @@
   <para>
    &minvm; is delivered as preconfigured and ready-to-run virtual machine
    images. The system comes with the <systemitem>&jeosfirstboot;</systemitem>
-   wizard for configuring system locales and the root password during the first
+   wizard for configuring system locales and the &rootuser; password during the first
    boot. &minvm; ships with the SSH server enabled and excluded from the
    firewall configuration. The supplied &kiwi; templates make it possible to
    create customized &minvm; images.
@@ -110,7 +110,7 @@
       <para>
        &minvm; comes with the <package>&jeosfirstboot;</package> tool, which can
        be used to configure basic settings during the first boot. This includes
-       keyboard layout and language, time zone, and root password.
+       keyboard layout and language, time zone, and &rootuser; password.
       </para>
       <para>
        The default network configuration is set to use DHCP, and the system
@@ -150,7 +150,7 @@
       </para>
       <note>
       <para>
-      The <package>&jeosfirstboot;</package>, <package>jeos-licenses</package>, and <package>live-langset-data</package> receive updates only if the Development Tools Module is enabled. However, these packages are not essential for running &minvm; instances, so they can be removed or left untouched.
+      The <package>&jeosfirstboot;</package>, <package>jeos-licenses</package> and <package>live-langset-data</package> packages receive updates only if the Development Tools Module is enabled. However, these packages are not essential for running &minvm; instances, so they can be removed or left untouched.
       </para>
       </note>
      </listitem>
@@ -551,7 +551,7 @@ runcmd:
    <step>
     <para>
      Select the created storage pool, click the <guimenu>Browse Local</guimenu> button, and select the &minvm; qcow2
-     image. Specify the correct operating system in the <guimenu>Choose the operating system your are installing</guimenu> field, and click <guimenu>Forward</guimenu>.
+     image. Specify the correct operating system in the <guimenu>Choose the operating system you are installing</guimenu> field, and click <guimenu>Forward</guimenu>.
     </para>
    </step>
    <step>
@@ -660,7 +660,7 @@ runcmd:
 &minvm; comes with the &combustion; configuration tool that makes it possible to configure the system on first boot using a dedicated script file. Using &combustion; instead of &jeosfirstboot; allows you to automatically apply identical configuration to multiple &minvm; instances.
   </para>
   <para> 
-    To trigger &combustion; tool in &kvm;, use the <command>qemu</command> command with the <parameter>fw_cfg</parameter> parameter that specifies the location of the <filename>script</filename> file.
+    To trigger the &combustion; tool in &kvm;, use the <command>qemu</command> command with the <parameter>fw_cfg</parameter> parameter that specifies the location of the <filename>script</filename> file.
   </para>
   <para>
     To see how this works in practice, you can use a simple &combustion; script that automatically adds the &rootuser; user to the &minvm; instance running in &qemu;.
@@ -670,7 +670,7 @@ runcmd:
      </para>
 <screen>echo 'root:$5$.wn2BZHlEJ5R3B1C$TAHEchlU.h2tvfOpOki54NaHpGYKwdNhjaBuSpDotD7' | chpasswd -e</screen>
   <para>
-    Run a new vistual machine based on &minvm; in &qemu; using the following command (replace <replaceable>IMAGE</replaceable> and <replaceable>SCRIPT</replaceable> with the pathname of the <filename>.qcow2</filename> image and the <filename>script</filename> file):
+    Run a new virtual machine based on &minvm; in &qemu; using the following command (replace <replaceable>IMAGE</replaceable> and <replaceable>SCRIPT</replaceable> with the path name of the <filename>.qcow2</filename> image and the <filename>script</filename> file):
   </para>
 <screen>&prompt.user;qemu-system-x86_64 \
   -enable-kvm \