Fix a few broken links in the documentation

docs/source/conf.py

@@ -74,6 +74,7 @@
     "enum_tools.autoenum",
     "nbsphinx",
     "pydata_sphinx_theme",
+    "sphinx.ext.autosectionlabel",
     "sphinx.ext.autodoc",
     "sphinx.ext.graphviz",
     "sphinx.ext.intersphinx",

docs/source/user_guide/custom_operators.rst

@@ -88,7 +88,7 @@ In the various properties for the class, you specify the following:
 - List for operator properties, including name to use in the documentation and code generation and the
   operator category. The optional ``license`` property allows to 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:`target_to_ansys_license_increments_list`)
+  currently accepted by DPF (see :ref:`here<target_to_ansys_license_increments_list>`)
 
 For comprehensive examples on writing operator plugins, see :ref:`python_operators`.
 

docs/source/user_guide/operators.rst

@@ -60,8 +60,8 @@ which is progressively enhanced, see :ref:`ref_dpf_operators_reference`.
 Create operators
 ~~~~~~~~~~~~~~~~
 Each operator is of type :ref:`ref_operator`. You can create an instance 
-in Python with any of the derived classes available in the 
-package :ref:`ref_operators_package` or directly with the :ref:`ref_operator`
+in Python with any of the derived classes available in the
+:ref:`ansys.dpf.core.operators package` or directly with the :ref:`ref_operator`
 class using the internal name string that indicates the operator type. 
 For more information, see :ref:`ref_dpf_operators_reference`.
 
@@ -446,5 +446,5 @@ Python client is not on the same machine as the server:
 API reference
 ~~~~~~~~~~~~~
 For a list of all operators in DPF, see :ref:`ref_dpf_operators_reference` 
-or the package :ref:`ref_operators_package`.  For more information about the
+or the package :ref:`ansys.dpf.core.operators package`.  For more information about the
 class itself, see :ref:`ref_operator`.