Fixed issues reported by pre-commit

agronholm · Aug 12, 2023 · a9cd7cd · a9cd7cd
1 parent bc8100f
commit a9cd7cd
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 3 deletions.
diff --git a/docs/modules/executors/base.rst b/docs/modules/executors/base.rst
@@ -8,4 +8,3 @@ Module Contents
 
 .. autoclass:: BaseExecutor
     :members:
-
diff --git a/docs/modules/schedulers/qt.rst b/docs/modules/schedulers/qt.rst
@@ -13,7 +13,7 @@ API
 Introduction
 ------------
 
-QtScheduler lets you integrate APScheduler with your `PySide2 <https://wiki.qt.io/Qt_for_Python>`, `PySide <https://en.wikipedia.org/wiki/PySide>` or
+QtScheduler lets you integrate APScheduler with your `PySide <https://en.wikipedia.org/wiki/PySide>`_ or
 `PyQt <http://www.riverbankcomputing.co.uk/software/pyqt/intro>`_ application.
 
 .. list-table::

diff --git a/docs/userguide.rst b/docs/userguide.rst
@@ -420,7 +420,7 @@ job's ``misfire_grace_time`` option (which can be set on per-job basis or global
 scheduler) to see if the execution should still be triggered. This can lead into the job being
 executed several times in succession.
 
-If this behavior is undesirable for your particular use case, it is possible to use `coalescing` to
+If this behavior is undesirable for your particular use case, it is possible to use ``coalescing`` to
 roll all these missed executions into one. In other words, if coalescing is enabled for the job and
 the scheduler sees one or more queued executions for the job, it will only trigger it once. No
 misfire events will be sent for the "bypassed" runs.