review feedback-1

SUSE · Dec 10, 2024 · 2938f4a · 2938f4a
1 parent d67ae2b
commit 2938f4a
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 7 deletions.
diff --git a/articles/systemd-securing.asm.xml b/articles/systemd-securing.asm.xml
@@ -70,7 +70,7 @@
       -->
       <meta name="architecture" its:translate="no">
         <phrase>&x86-64;</phrase>
-        <phrase>&power;</phrase>
+        <phrase>&power;</phrase>How to improve the overall exposure
       </meta>
       <meta name="productname" its:translate="no">
         <productname version="16.0" os="sles">&productname;</productname>

diff --git a/concepts/systemd-securing.xml b/concepts/systemd-securing.xml
@@ -52,7 +52,7 @@
      A detailed analysis of the security settings is executed and displayed.
      If a service unit is not specified, all currently loaded, long-running service units are inspected and the results are displayed in a terse table.
      </para>
-<para>The command upon checking the security settings, assigns a numeric value , also known as <emphasis>exposure level</emphasis>.
+<para>Upon checking the security settings, the command assigns a numeric value , also known as <emphasis>exposure level</emphasis>.
   This value is dependent on how important a setting is. It then calculates an overall exposure level for the whole unit. This value ranges
   from 0.0-10.0, which is an indicator of how exposed a service is security wise.
   High exposure levels indicate that the service might benefit from additional security settings.

diff --git a/tasks/systemd-example-secure-service.xml b/tasks/systemd-example-secure-service.xml
@@ -49,7 +49,7 @@ NAME                DESCRIPTION                              EXPOSURE
                </step>
               </procedure>
                <section xml:id="improving-overall-exposure">
-                <title>How to improve the overall exposure with options?</title>
+                <title>How to improve the overall exposure</title>
                 <para>Use the command <command>systemd-analyze security</command> to analyze the security settings of a
                 &systemd; service. For example: </para>
 <screen>
@@ -126,17 +126,17 @@ NAME                DESCRIPTION                              EXPOSURE
                         <command>pscap</command> tool from the <package>libcap-ng-utils</package> package.
                       </para>
                     </tip>
-                    <tip>
+
                       <para>
-                        The <literal>~</literal> prefix inverts the meaning of the option&mdash;instead of
-                        listing all capabilities that the service retains, you may list the ones it does not
+                        The <literal>~</literal> prefix inverts the meaning of the option&mdash;. Instead of
+                        listing all capabilities that the service retains, you can list the ones it does not
                         retain:
                       </para>
 <screen>...
 [Service]
 CapabilityBoundingSet=~CAP_SYS_PTRACE
 ...</screen>
-                    </tip>
+
                   </listitem>
 
                 </varlistentry>