DOCS: Fixing Model Representation - porting to master (#13146)

* DOCS: Fixing Model Representation - porting to master

Fixing the snippets in tabs.

Porting:
https://github.com/openvinotoolkit/openvino/pull/13088

* Additional Resources

Co-authored-by: Karol Blaszczak <karol.blaszczak@intel.com>

docs/OV_Runtime_UG/model_representation.md

@@ -11,10 +11,10 @@ Each operation in `ov::Model` has the `std::shared_ptr<ov::Node>` type.
 ## How OpenVINO Runtime Works with Models
 
 OpenVINO™ Runtime enables you to use different approaches to work with model inputs/outputs:
- - The `ov::Model::inputs()`/`ov::Model::outputs()` methods are used to get vectors of all input/output ports.
- - For a model that has only one input or output, you can use the `ov::Model::input()` or `ov::Model::output()` methods without any arguments to get input or output port respectively.
- - The `ov::Model::input()` and `ov::Model::output()` methods can be used with the index of inputs or outputs from the framework model to get specific ports by index.
- - You can use the tensor name of input or output from the original framework model together with the `ov::Model::input()` or `ov::Model::output()` methods to get specific ports. It means that you do not need to have any additional mapping of names from framework to OpenVINO as it was before. OpenVINO™ Runtime allows the usage of native framework tensor names, for example:
+   - The `ov::Model::inputs()`/`ov::Model::outputs()` methods are used to get vectors of all input/output ports.
+   - For a model that has only one input or output, you can use the `ov::Model::input()` or `ov::Model::output()` methods without any arguments to get input or output port respectively.
+   - The `ov::Model::input()` and `ov::Model::output()` methods can be used with the index of inputs or outputs from the framework model to get specific ports by index.
+   - You can use the tensor name of input or output from the original framework model together with the `ov::Model::input()` or `ov::Model::output()` methods to get specific ports. It means that you do not need to have any additional mapping of names from framework to OpenVINO as it was before. OpenVINO™ Runtime allows the usage of native framework tensor names, for example:
 
         @sphinxtabset
 
@@ -32,6 +32,7 @@ OpenVINO™ Runtime enables you to use different approaches to work with model i
 
         @endsphinxtabset
 
+
 For details on how to build a model in OpenVINO™ Runtime, see the [Build a Model in OpenVINO™ Runtime](@ref ov_ug_build_model) section.
 
 OpenVINO™ Runtime model representation uses special classes to work with model data types and shapes. The `ov::element::Type` is used for data types. See the section below for representation of shapes.
@@ -192,7 +193,7 @@ OpenVINO™ provides several debug capabilities:
 
      @endsphinxtab
 
-## See Also
+## Additional Resources
 
 * [Available Operation Sets](../ops/opset.md)
 * [OpenVINO™ Runtime Extensibility Developer Guide](../Extensibility_UG/Intro.md)