[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

docs/api/clients.rst

@@ -29,7 +29,7 @@ Bots
 
     .. automethod:: Bot.listen(name=None)
         :decorator:
-    
+
     .. automethod:: Bot.once(name=None, check=None)
         :decorator:
 

docs/api/events.rst

@@ -9,8 +9,8 @@ This section outlines the different types of events listened by :class:`Client`.
 
 There are 4 ways to register an event, the first way is through the use of
 :meth:`Client.event`. The second way is through subclassing :class:`Client` and
-overriding the specific events. The third way is through the use of :meth:`Client.listen`, 
-which can be used to assign multiple event handlers instead of only one like in :meth:`Client.event`. 
+overriding the specific events. The third way is through the use of :meth:`Client.listen`,
+which can be used to assign multiple event handlers instead of only one like in :meth:`Client.event`.
 The fourth way is through the use of :meth:`Client.once`, which serves as a one-time event listener. For example:
 
 .. code-block:: python
@@ -40,7 +40,7 @@ The fourth way is through the use of :meth:`Client.once`, which serves as a one-
     @client.listen()
     async def on_message(message: discord.Message):
         print(f"Received {message.content}")
-    
+
     # Runs only for the 1st 'on_message' event. Can be useful for listening to 'on_ready'
     @client.once()
     async def message(message: discord.Message):

docs/ext/commands/api.rst

@@ -48,7 +48,7 @@ Bot
 
     .. automethod:: Bot.listen(name=None)
         :decorator:
-    
+
     .. automethod:: Bot.once(name=None, check=None)
         :decorator: