Apply suggestions from code review

Co-authored-by: Daria Vladykina <[email protected]>

Author: lvicoun

articles/customizing-products-images.asm.xml

@@ -78,8 +78,7 @@
         <productname version="6.2">&slm;</productname>
       </meta>
       <meta name="title" its:translate="yes">Customizing &productname; on Premises</meta>
-      <meta name="description" its:translate="yes">How to customize deployment images, kernel modules and kernel drivers
-      modules a </meta>
+      <meta name="description" its:translate="yes">How to customize deployment images, kernel modules and kernel drivers </meta>
       <meta name="social-descr" its:translate="yes">Customize deployment images, kernel modules and kernel drivers</meta>
       <!-- suitable categories has to be identical with the category selected in the docserv config -->
       <meta name="category" its:translate="no">
@@ -122,7 +121,7 @@
           <term>WHY?</term>
           <listitem>
             <para>
-              You want to create an deployment image completely suited to your needs.
+              You want to create a deployment image completely suited to your needs.
             </para>
           </listitem>
         </varlistentry>

concepts/customizing-products-drivers.xml

@@ -18,7 +18,7 @@
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:trans="http://docbook.org/ns/transclusion">
   <info>
-    <title>Creating custom dirvers</title><!-- can be changed via merge in the assembly -->
+    <title>Creating custom drivers</title><!-- can be changed via merge in the assembly -->
     <!--add author's email address-->
     <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract><!-- can be changed via merge in the assembly -->
@@ -28,10 +28,10 @@
     </abstract>
   </info>
   <para>
-Installing third-party hardware drivers into a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;.
+Installing third-party hardware drivers in a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;.
   </para>
   <para>
-    For a detailed description of the &suse; SolidDriver Program refer to the <link
+    For a detailed description of the &suse; SolidDriver Program, refer to the <link
     xlink:href="https://drivers.suse.com/doc/SolidDriver/index.html">official documentation of the
     program</link>.
   </para>

concepts/customizing-products-identification.xml

@@ -30,7 +30,7 @@ in the assembly -->
    and mitigate risk. However, when &slea; family products are being bundled with a
    system or integrated into a solution by an OEM, the system or solution needs to state the
    OEM status to customers, users and any compliance team. An important reason for this is that the
-   terms and conditions of an OEM license agreement usually differ from a common end user
+   terms and conditions of an OEM license agreement usually differ from a common end-user
    license agreement (EULA).
       </para>
     </abstract>
@@ -49,7 +49,7 @@ in the assembly -->
      the OEM solution, the file <filename>/etc/os-release</filename> shall be amended. For details
      about the file structure, refer to the <link
      xlink:href="https://documentation.suse.com/sles/16.0/html/SLE-os-identification">&slea;
-     OS indetification</link> .</para>
+     OS identification</link>.</para>
 
      <para>The definition of <filename>/etc/os-release</filename> does not cover OEM identification.
     However, custom values can be added when correctly prefixed. We suggest OEMs to introduce:</para>
@@ -75,7 +75,7 @@ The attribute refers to the main support page for the OEM operating system.
     <term>SUSE_OEM_BUG_REPORT_URL</term>
     <listitem>
       <para>
-The attribute refersto the main bug reporting page for the OEM operating system.
+The attribute refers to the main bug reporting page for the OEM operating system.
       </para>
     </listitem>
   </varlistentry>
@@ -106,8 +106,8 @@ eth0: \4{eth0} \6{eth0}
      <package>*-release</package> package from the respective product provided by &suse; may be used
     as a template. </para>
 
-   <para>It is important for the OEM to make sure <emphasis role="strong">no</emphasis> &suse;
-    originated files can be found in <filename>/etc/products.d/</filename> that would identify the
+   <para>It is important for the OEM to make sure <emphasis role="strong">no</emphasis>
+     &suse;-originated files can be found in <filename>/etc/products.d/</filename> that would identify the
     system as a &slea; system. Instead, the information contained in the file needs
     to come from the OEM and explicitly identify the OEM system.</para>
   </section>

concepts/customizing-products-images-introduction.xml

@@ -29,7 +29,7 @@
   </info>
   <para>
     This article explains how to transform the provided raw OS image into a purpose-built system. The
-    process may involve installing necessary software from RPMs and applying custom configurations
+    process may involve installing the necessary software from RPMs and applying custom configurations
     for standard deployments. For specialized hardware not supported by the default image, we will
     also cover how to build and integrate custom kernel modules and drivers to ensure full system
     functionality.

concepts/customizing-products-kernel.xml

@@ -23,7 +23,7 @@
     <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract><!-- can be changed via merge in the assembly -->
       <para>
-       The topic serves as a link to a SBP.
+       The topic serves as a link to an SBP.
       </para>
     </abstract>
   </info>
@@ -34,6 +34,6 @@ provides detailed guidelines on this process. This comprehensive guide covers ev
 background on kernel ABI stability to the step-by-step process of building, packaging, signing, and
 deploying your own kernel modules correctly. For details, refer to the <link
 xlink:href="https://documentation.suse.com/en-us/sbp/systems-management/html/SBP-KMP-Manual-SLE12SP2/index.html">Kernel
-Modules Packages Manual</link>.
+Module Packages Manual</link>.
   </para>
 </topic>