Fix typos in counter documentation (#101)

Author: solidpixel

docs/mali-g310_counter_reference.html

@@ -111,7 +111,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Valhall memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -183,10 +183,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Valhall shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g31_counter_reference.html

@@ -108,7 +108,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Bifrost memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -180,10 +180,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Bifrost shader core" src="./images/bifrost-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g510_counter_reference.html

@@ -111,7 +111,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Valhall memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -183,10 +183,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Valhall shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g51_counter_reference.html

@@ -108,7 +108,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Bifrost memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -180,10 +180,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Bifrost shader core" src="./images/bifrost-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g52_counter_reference.html

@@ -108,7 +108,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Bifrost memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -180,10 +180,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Bifrost shader core" src="./images/bifrost-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g57_counter_reference.html

@@ -108,7 +108,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Valhall memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -180,10 +180,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Valhall shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g610_counter_reference.html

@@ -111,7 +111,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Valhall memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -183,10 +183,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Valhall shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g615_counter_reference.html

@@ -111,7 +111,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="Valhall memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -183,10 +183,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="Valhall shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g620_counter_reference.html

@@ -112,7 +112,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="5th Generation memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -184,10 +184,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="5th Generation shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>

docs/mali-g625_counter_reference.html

@@ -112,7 +112,7 @@ <h4>GPU queues</h4>
 workload. In addition you can see if your application is using barriers
 efficiently, allowing the queues to run their workloads in parallel.</p>
 <h3>Profiling GPU memory bandwidth</h3>
-<p>GPUs are a data-plane processors, so memory access efficiency is an important
+<p>GPUs are data-plane processors, so memory access efficiency is an important
 factor for overall performance.</p>
 <p><img alt="5th Generation memory system" src="./images/bifrost-memory-system.svg" /></p>
 <p>Memory system performance outside of the GPU cannot be directly observed via
@@ -184,10 +184,10 @@ <h3>Profiling workload</h3>
 context of API constructs, such as vertices, triangles, and pixels making it
 easier for developers to understand the feedback.</p>
 <p><img alt="5th Generation shader core" src="./images/valhall-shader-core.svg" /></p>
-<p>Supplementing the workload size counters, the Arm GPU also provide counters
-that indicate areas where content is not following best practice guidelines.
+<p>Supplementing the workload size counters, Arm GPUs also provide counters that
+indicate areas where content is not following best practice guidelines.
 Improving these best practice metrics will nearly always improve your
-application's performance.</p>
+application's performance or energy efficiency.</p>
 </div>
 <div class="lgc-section">
 <h2 id="s_gpufrontend">GPU Front-end <span data-bs-toggle="tooltip" data-bs-delay="400" data-bs-placement="right" title="Copy to clipboard"><a class="lgc-link-copy link-secondary"><i class="fa-solid fa-link"></i></a></span></h2>