Proofreading pass 4

Author: sgolebiewski-intel

docs/articles_en/learn-openvino/openvino-samples/benchmark-tool.rst

@@ -68,39 +68,36 @@ Basic Usage
          ./benchmark_app -m model.xml
 
 
-By default, the application will load the specified model onto the CPU and perform
-inference on batches of randomly-generated data inputs for 60 seconds. As it loads,
-it prints information about the benchmark parameters. When the benchmark is completed,
-it reports the minimum, average, and maximum inference latency and the average throughput.
+By default, the application loads the specified model and performs
+inference on batches of randomly-generated data inputs on CPU for 60 seconds.
+It displays information about the benchmark parameters as it loads the model.
+When the benchmark is completed, it reports the minimum, average, and maximum inference
+latency and the average throughput.
 
 You may be able to improve benchmark results beyond the default configuration by
 configuring some of the execution parameters for your model. For example, you can
 use "throughput" or "latency" performance hints to optimize the runtime for higher
 FPS or reduced inference time. Read on to learn more about the configuration
-options available with ``benchmark_app``.
+options available for ``benchmark_app``.
 
 Configuration Options
 #####################
 
-The benchmark app provides various options for configuring execution parameters.
-This section covers key configuration options for easily tuning benchmarks to
-achieve better performance on your device. A list of all configuration options
+You can easily configure and fine-tune benchmarks with various execution parameters,
+for example to achieve better performance on your device. The list of all configuration options
 is given in the :ref:`Advanced Usage <advanced-usage-benchmark>` section.
 
 Performance hints: latency and throughput
 +++++++++++++++++++++++++++++++++++++++++
 
-The benchmark app allows users to provide high-level "performance hints" for
-setting latency-focused or throughput-focused inference modes. This hint causes
-the runtime to automatically adjust runtime parameters, such as the number of
-processing streams and inference batch size, to prioritize for reduced latency
-or high throughput.
+With high-level "performance hints", which automatically adjust parameters such as the
+number of processing streams and inference batch size, you can aim for low-latency
+or high-throughput inference.
 
 The performance hints do not require any device-specific settings and they are
-completely portable between devices. Parameters are automatically configured
-based on whichever device is being used. This allows users to easily port
-applications between hardware targets without having to re-determine the best
-runtime parameters for the new device.
+completely portable between devices. The parameters are automatically configured
+based on the device. Therefore, you can easily port applications between hardware targets
+without having to re-determine the best runtime parameters for a new device.
 
 If not specified, throughput is used as the default. To set the hint explicitly,
 use ``-hint latency`` or ``-hint throughput`` when running ``benchmark_app``:
@@ -125,8 +122,12 @@ use ``-hint latency`` or ``-hint throughput`` when running ``benchmark_app``:
 
 .. note::
 
-   It is up to the user to ensure the environment on which the benchmark is running is optimized for maximum performance. Otherwise, different results may occur when using the application in different environment settings (such as power optimization settings, processor overclocking, thermal throttling).
-   When you specify single options multiple times, only the last value will be used. For example, the ``-m`` flag:
+   Make sure the environment is optimized for maximum performance when benchmark is running.
+   Otherwise, different environment settings, such as power optimization settings, processor
+   overclocking, or thermal throttling may give different results.
+
+   When you specify single options multiple times, only the last value will be used.
+   For example, the ``-m`` flag:
 
    .. tab-set::