Typo fixes / more direct voice (#620)

Author: dirkmueller

concepts/ansible-role-suseconnect.xml

@@ -28,7 +28,7 @@
   <para>You can use this role to:</para>
   <itemizedlist>
   <listitem><para>Register a SUSE system to the SCC or  servers.</para></listitem>
-  <listitem><para>Activate or remove of specific add-on products or modules.</para></listitem>
+  <listitem><para>Activate or remove specific add-on products or modules.</para></listitem>
   <listitem><para>Deregister systems or products.</para></listitem>
   <listitem><para>Support transactional update register SLE-MICRO.</para></listitem>
   <listitem><para>Recheck tasks to ensure a smooth registration process.</para></listitem>
@@ -81,7 +81,7 @@
         name: suse.linux_system_roles.suseconnect
 </screen>
   <itemizedlist>
-    <listitem><para><literal>suseconnect_deregister: true</literal>: instructs the system to deactivate its base subscription and remove it from the the SCC or SMT servers.
+    <listitem><para><literal>suseconnect_deregister: true</literal>: instructs the system to deactivate its base subscription and remove it from the SCC or SMT servers.
      <literal>suseconnect_deregister</literal> is a <literal>Boolean</literal> datatype and accepts values <literal>false</literal> and <literal>true</literal>. When set to
      <literal>true</literal>, it executes the necessary SUSEConnect command to deregister the system's base product subscription. Default is <literal>false</literal>. </para></listitem>
       </itemizedlist>

tasks/deploy-sap-ansible-aws.xml

@@ -145,11 +145,11 @@ For this procedure:</para>
     <listitem><para>Scenario passwords encrypted in Ansible vault.</para></listitem>
     <listitem><para>Scenario non-sensitive variables without using Ansible vault.</para></listitem>
   </itemizedlist>
-  <para>In this procedure, we use a simplified variant for encrypting whole files.</para>
+  <para>This procedure uses a simplified variant for encrypting whole files.</para>
   </step>
     </substeps>
   </step>
-<step><para>Copy the variable files from the source. Since we are provisioning new servers in AWS, only two variable files are required:</para>
+<step><para>Copy the variable files from the source. Since this procedure provisions new servers in AWS, only two variable files are required:</para>
 <itemizedlist><listitem><para><literal>ansible_extravars.yml</literal> contains scenario-specific variables.</para></listitem>
   <listitem><para><literal>ansible_extravars_aws_ec2_vs.yml</literal> contains platform-specific variables.</para></listitem>
 </itemizedlist>

tasks/networkmanager-nmcli-configure.xml

@@ -311,7 +311,7 @@ creation process or beforehand.</para></listitem>
 <step><para>To configure <literal>p2p-dev-wlan0</literal> as a port, 
 create a connection profile:</para>
 <screen>&prompt.sudo;nmcli connection add type wifi-p2p slave-type bond con-name bond0-port1 ifname p2p-dev-wlan0 master bond0</screen>
-<para>A new profile is created for <literal>p2p-dev-wlan0</literal> and added to the <literal>bond0</literal> connection. The name of the bond is <literal>bond0</literal>.</para></step>
+<para>This creates a new profile for <literal>p2p-dev-wlan0</literal> and adds it to the <literal>bond0</literal> connection. The name of the bond is <literal>bond0</literal>.</para></step>
 <step><para>To assign <literal>virbr0</literal> to a bond:</para>
 <screen>&prompt.sudo;nmcli connection modify virbr0 master bond0</screen>
 <para>The  connection profile for <literal>virbr0</literal> is added to the <literal>bond0</literal> connection.</para>
@@ -582,7 +582,7 @@ but you have not created any bond0 in this section. -->
   <step><para>Create a bridge interface:</para>
   <screen>&prompt.sudo;nmcli connection add type bridge con-name <replaceable>CONNECTION_NAME</replaceable> ifname <replaceable>BRIDGE_NAME</replaceable></screen>
   <para>
-   For example, we created a bridge: <literal>bridge0</literal> by running the command:
+   For example, create a bridge <literal>bridge0</literal> by running the command:
   </para>
   <screen>&prompt.sudo;nmcli connection add type bridge con-name bridge0 ifname bridge0</screen>
   </step>
@@ -606,11 +606,11 @@ connection profile).
 </step>
 <step><para>Add interfaces to the bridge:</para>
 <screen>&prompt.sudo;nmcli connection add type wifi-p2p slave-type bridge con-name bridge0-port1 ifname p2p-dev-wlan0 master bridge0</screen>
-<para>A new profile is created for p2p-dev-wlan0 and added to the <literal>bridge0</literal> connection.</para></step>
+<para>This creates a new profile for p2p-dev-wlan0 and adds it to the <literal>bridge0</literal> connection.</para></step>
 <step><para>To assign an existing connection to the bridge:</para>
 <screen>&prompt.sudo;nmcli connection modify bond0 master bridge0</screen>
-<para>The connection profile for <literal>bond0</literal>
-  is added to the <literal>bridge0</literal> connection.</para>
+<para>This adds the connection profile for <literal>bond0</literal>
+  to the <literal>bridge0</literal> connection.</para>
 </step>
 <step><para>Restart the connection:</para>
 <screen>&prompt.sudo;nmcli connection up bond0</screen></step>