Docs: Update the doc on how to manually set operations affinity & fix some spelling errors

docs/OV_Runtime_UG/hetero_execution.md

@@ -31,6 +31,9 @@ Following the OpenVINO™ naming convention, the Hetero execution plugin is assi
 #### The Manual Mode
 It assumes setting affinities explicitly for all operations in the model using `ov::Node::get_rt_info` with the `"affinity"` key. 
 
+If you assign specific operation to a specific device, make sure that the device actually supports the operation. 
+Randomly selecting operations and setting affinities may lead to decrease in model accuracy. To avoid that, try to set the related operations or subgraphs of this operation to the same affinity, such as the constant operation that will be folded into this operation.
+
 @sphinxtabset
 
 @sphinxtab{C++}

docs/OV_Runtime_UG/supported_plugins/GPU.md

@@ -160,7 +160,7 @@ Alternatively, it can be enabled explicitly via the device notion, for example `
 
 @endsphinxtab
 
-@sphinxtab{Bacthing via throughput hint}
+@sphinxtab{Batching via throughput hint}
 
 @sphinxtabset
 

docs/OV_Runtime_UG/supported_plugins/GPU_RemoteTensor_API.md

@@ -108,7 +108,7 @@ To request the current default context of the plugin, use one of the following m
 
 @endsphinxtab
 
-@sphinxtab{Bacthing via throughput hint}
+@sphinxtab{Batching via throughput hint}
 
 @snippet docs/snippets/gpu/remote_objects_creation.cpp default_context_from_model