From b20d6095ba311134acc0317e26de2ff4d0e6714d Mon Sep 17 00:00:00 2001
From: Souvik Sarkar <souvik.sarkar@suse.com>
Date: Thu, 13 Jul 2023 22:24:09 +0530
Subject: [PATCH] Vale style checks for tuning guide

---
 xml/tuning_oprofile.xml | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/xml/tuning_oprofile.xml b/xml/tuning_oprofile.xml
index a59bb033e3..b3f4e7b4ff 100644
--- a/xml/tuning_oprofile.xml
+++ b/xml/tuning_oprofile.xml
@@ -27,8 +27,8 @@
    </para>
         <para>
     It is not necessary to recompile or use wrapper libraries to
-    use &oprof;. Not even a kernel patch is needed. Usually, when
-    profiling an application, a small overhead is expected, depending on the
+    use &oprof;. Not even a kernel patch is needed. When
+    profiling an application, you can expect a small overhead, depending on the
     workload and sampling frequency.
    </para>
       </abstract>
@@ -81,7 +81,7 @@
 
   <para>
    It is useful to install the <filename>*-debuginfo</filename> package for
-   the respective application you want to profile. If you want to profile
+   the respective application you want to profile. To profile
    the kernel, you need the <filename>debuginfo</filename> package as well.
   </para>
  </sect1>
@@ -145,8 +145,7 @@
     </term>
     <listitem>
      <para>
-      Converts sample database files from a foreign binary format to the
-      native format.
+      Converts sample database files from a foreign binary format to the format specific to the platform.
      </para>
     </listitem>
    </varlistentry>
@@ -168,14 +167,14 @@
    With &oprof;, you can profile both the kernel and applications. When
    profiling the kernel, tell &oprof; where to find the
    <filename>vmlinuz*</filename> file. Use the <option>--vmlinux</option>
-   option and point it to <filename>vmlinuz*</filename> (usually in
+   option and point it to <filename>vmlinuz*</filename> (generally available in
    <filename>/boot</filename>). If you need to profile kernel modules,
    &oprof; does this by default. However, make sure you read
    <link xlink:href="http://oprofile.sourceforge.net/doc/kernel-profiling.html"/>.
   </para>
 
   <para>
-   Applications usually do not need to profile the kernel, therefore you
+   Most applications do not need to profile the kernel, therefore you
    should use the <option>--no-vmlinux</option> option to reduce the amount
    of information.
   </para>
@@ -194,7 +193,7 @@
     </step>
     <step>
      <para>
-      Decide if you want to profile with or without the Linux kernel:
+      Decide whether to profile with or without the Linux kernel:
      </para>
      <substeps performance="required">
       <step>
@@ -406,7 +405,7 @@ BR_MISS_PRED_RETIRED: (counter: all))
    <option>--session-dir</option>, <command>operf</command> has written its
    data to <replaceable>CUR_DIR</replaceable>/oprofile_data/samples/current,
    and the reporting tools <command>opreport</command> and
-   <command>opannotate</command> will look there by default.
+   <command>opannotate</command> looks there by default.
   </para>
 
   <para>
@@ -429,8 +428,8 @@ BR_MISS_PRED_RETIRED: (counter: all))
 
   <para>
    The option <option>--base-dir</option> contains a comma separated list of
-   paths which is stripped from debug source files. These paths were
-   searched prior to looking in <option>--search-dirs</option>. The
+   paths which is stripped from debug source files. These paths are
+   searched before looking in <option>--search-dirs</option>. The
    <option>--search-dirs</option> option is also a comma separated list of
    directories to search for source files.
   </para>