Update headings and some wordings for Transition Guide (#11065)

* updates

* update

* merge from releases/22/1

* update heading

* update headings and some wordings

docs/OV_Runtime_UG/migration_ov_2_0/common_inference_pipeline.md

@@ -1,6 +1,6 @@
 # Inference Pipeline {#openvino_2_0_inference_pipeline}
 
-Usually to inference model with the OpenVINO™ Runtime an user needs to do the following steps in the application pipeline:
+Usually to infer models with OpenVINO™ Runtime, you need to do the following steps in the application pipeline:
 - 1. Create Core object
  - 1.1. (Optional) Load extensions
 - 2. Read model from the disk
@@ -11,7 +11,7 @@ Usually to inference model with the OpenVINO™ Runtime an user needs to do the
 - 6. Start inference
 - 7. Process the inference results
 
-Code snippets below cover these steps and show how application code should be changed for migration to OpenVINO™ Runtime 2.0.
+The following code shows how to change the application code in each step to migrate to OpenVINO™ Runtime 2.0.
 
 ## 1. Create Core
 

docs/OV_Runtime_UG/migration_ov_2_0/configure_devices.md

@@ -1,4 +1,4 @@
-# Configure devices {#openvino_2_0_configure_devices}
+# Configuring Devices {#openvino_2_0_configure_devices}
 
 ### Introduction
 

docs/OV_Runtime_UG/migration_ov_2_0/graph_construction.md

@@ -1,4 +1,4 @@
-# Model creation in runtime {#openvino_2_0_model_creation}
+# Model Creation in Runtime {#openvino_2_0_model_creation}
 
 OpenVINO™ Runtime API 2.0 includes nGraph engine as a common part. The `ngraph` namespace was changed to `ov`, all other ngraph API is preserved as is.
 Code snippets below show how application code should be changed for migration to OpenVINO™ Runtime API 2.0.

docs/OV_Runtime_UG/migration_ov_2_0/intro.md

@@ -1,4 +1,4 @@
-# OpenVINO™ 2.0 Transition Guide {#openvino_2_0_transition_guide}
+# OpenVINO™ Transition Guide for API 2.0 {#openvino_2_0_transition_guide}
 
 @sphinxdirective
 
@@ -24,7 +24,7 @@ Older versions of OpenVINO™ (prior to 2022.1) required to change the logic of
 - Inference Engine API (`InferenceEngine::CNNNetwork`) also applied some conversion rules for input and output precisions because of device plugins limitations.
 - Users need to specify input shapes during model conversions in Model Optimizer and work with static shapes in the application.
 
-OpenVINO™ introduces API 2.0 to align logic of working with model as it is done in the frameworks - no layout and precision changes, operates with tensor names and indices to address inputs and outputs. OpenVINO Runtime is composed of Inference Engine API used for inference and nGraph API targeted to work with models, operations. The API 2.0 has common structure, naming convention styles, namespaces, removes duplicated structures. See [How to migrate to OpenVINO API v2](common_inference_pipeline.md) for details.
+OpenVINO™ introduces API 2.0 (also called OpenVINO API v2) to align the logic of working with model as it is done in the frameworks - no layout and precision changes, operates with tensor names and indices to address inputs and outputs. OpenVINO Runtime is composed of Inference Engine API used for inference and nGraph API targeted to work with models and operations. API 2.0 has common structure, naming convention styles, namespaces, and removes duplicated structures. See [Changes to Inference Pipeline in OpenVINO API v2](common_inference_pipeline.md) for details.
 
 > **NOTE**: Most important is that your existing application can continue working with OpenVINO Runtime 2022.1 as it used to be, but we recommend migration to API 2.0 to unlock additional features like [Preprocessing](../preprocessing_overview.md) and [Dynamic shapes support](../ov_dynamic_shapes.md).
 
@@ -38,7 +38,7 @@ The IR v11 is supported by all OpenVINO Development tools including Post-Trainin
 
 ### IR v10 Compatibility
 
-OpenVINO API 2.0 also supports models in IR v10 for backward compatibility. So, if a user has an IR v10, it can be fed to OpenVINO Runtime as well (see [migration steps](common_inference_pipeline.md)).
+API 2.0 also supports models in IR v10 for backward compatibility. So, if a user has an IR v10, it can be fed to OpenVINO Runtime as well (see [migration steps](common_inference_pipeline.md)).
 
 Some OpenVINO Development Tools also support both IR v10 and IR v11 as an input:
 - Accuracy checker uses API 2.0 for model accuracy measurement by default, but also supports switching to API 1.0 using the `--use_new_api False` command line parameter. Both launchers accept IR v10 and v11, but in some cases configuration files should be updated. More details can be found in [Accuracy Checker documentation](https://github.com/openvinotoolkit/open_model_zoo/blob/releases/2022/1/tools/accuracy_checker/openvino/tools/accuracy_checker/launcher/openvino_launcher_readme.md).