diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index c8b2e4948..dc9ccc6bb 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -2,7 +2,7 @@ repos:
 
 
 - repo: https://github.com/psf/black
-  rev: 24.1.1  # IF VERSION CHANGES --> MODIFY "blacken-docs" MANUALLY AS WELL!!
+  rev: 24.2.0  # IF VERSION CHANGES --> MODIFY "blacken-docs" MANUALLY AS WELL!!
   hooks:
   - id: black
     args: [
@@ -14,7 +14,7 @@ repos:
   rev: 1.16.0
   hooks:
   - id: blacken-docs
-    additional_dependencies: [black==24.1.1]
+    additional_dependencies: [black==24.2.0]
 
 - repo: https://github.com/pycqa/isort
   rev: 5.13.2
@@ -44,7 +44,7 @@ repos:
   - id: debug-statements
 
 - repo: https://github.com/python-jsonschema/check-jsonschema
-  rev: 0.27.4
+  rev: 0.28.0
   hooks:
     - id: check-github-workflows
       name: "Check GitHub workflows"
diff --git a/doc/source/coding-style/deprecation.rst b/doc/source/coding-style/deprecation.rst
index e6f2041dc..e46c73b49 100644
--- a/doc/source/coding-style/deprecation.rst
+++ b/doc/source/coding-style/deprecation.rst
@@ -1,9 +1,8 @@
 Deprecation best practices
 ==========================
 
-While deprecation best practices are outlined in a `Stack
-Overflow Answer <https://stackoverflow.com/questions/2536307>`_ and
-in this `Deprecation library <https://deprecation.readthedocs.io/>`_ ,
+While deprecation best practices are outlined in 
+this `Deprecation library <https://deprecation.readthedocs.io/>`_ ,
 there is no official guidance on deprecating features within Python.
 Thus, this topic provides deprecation best practices for PyAnsys
 libraries. 
@@ -93,4 +92,4 @@ You then use this custom ``DeprecationError`` in place of an ``Exception``.
             This function has been deprecated.
 
         """
-        raise DeprecationError('`my_function` has been deprecated.')
\ No newline at end of file
+        raise DeprecationError("`my_function` has been deprecated.")