Apply suggestions from code review

Co-authored-by: Kathy Pippert <[email protected]>
ansys · Jan 8, 2025 · 4c06ea2 · 4c06ea2
1 parent 03fdf74
commit 4c06ea2
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/doc/source/getting_started/compatibility.rst b/doc/source/getting_started/compatibility.rst
@@ -23,7 +23,7 @@ version.
 
 As new features are developed, every attempt is made to ensure backward
 compatibility from the client to the server. Backward compatibility is generally ensured for
-the four latest Ansys versions. For example, the ``ansys-dpf-core`` module 0.8.0 version has been
+the four latest Ansys versions. For example, the ``ansys-dpf-core`` module 0.8.0 has been
 developed for Ansys 2023 R2 pre1 release, for 2023 R2 Ansys version. It is compatible with
 2023 R2, 2023 R1, 2022 R2 and 2022 R1 Ansys versions.
 

diff --git a/doc/source/user_guide/concepts/waysofusing.rst b/doc/source/user_guide/concepts/waysofusing.rst
@@ -5,7 +5,7 @@ DPF capabilities and scripting languages
 ========================================
 DPF is a framework that provides data computation capabilities. 
 
-DPF as a Framework
+DPF as a framework
 ------------------
 
 DPF application: kernel and operator libraries
@@ -40,7 +40,7 @@ These capabilities can be accessed through client APIs, as shown here:
 
 Note that **IronPython and CPython APIs are different**, each has specific syntax.
 
-The **list of available operators when using DPF is independent from the language or API which is used**, it only depends
+The **list of available operators when using DPF is independent from the language or API which is used**. It depends only
 on how the DPF application has been initialized.
 
 Most of the DPF capabilities can be accessed using the operators. For more information about the existing operators, see :ref:`ref_dpf_operators_reference`.

diff --git a/doc/source/user_guide/custom_operators.rst b/doc/source/user_guide/custom_operators.rst
@@ -86,7 +86,7 @@ In the various properties for the class, specify the following:
   and whether it is optional and/or ellipsis (meaning that the specification is valid for pins going from pin
   number *x* to infinity)
 - List for operator properties, including name to use in the documentation and code generation and the
-  operator category. The optional ``license`` property allows you to define a required license to check out
+  operator category. The optional ``license`` property lets you define a required license to check out
   when running the operator. Set it equal to ``any_dpf_supported_increments`` to allow any license
   currently accepted by DPF (see :ref:`here<target_to_ansys_license_increments_list>`)