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

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

Author: pre-commit-ci[bot]

docs/deployment/continuous-deployment.md

@@ -31,11 +31,9 @@ It has several significant benefits:
 ## Manual production re-deployment
 
 1. Trigger `:prod` images builds
-
    - Run [scripts/move_stable.py](https://github.com/packit/deployment/blob/main/scripts/move_stable.py) to move `stable` branches to a newer commit.
 
 2. Import images -> re-deploy
-
    - If you don't want to wait for [it to be done automatically](#continuous-deployment), you can
      [do that manually](#manually-import-a-newer-image) once the images are built (check Actions in each repo).
 

docs/deployment/resource-requirements.md

@@ -83,14 +83,12 @@ resource requirements.
 1. Request adjustments of the quotas such that we can have some buffer (database
    migrations, higher load on service, etc.), but also could **permanently**
    scale up the workers if we find service to be more reliable that way
-
    - Based on the calculations above, 2× the current quotas on memory would be
      sufficient, but if we were to scale the workers up too (and account for
      possible adjustments, e.g., Redict) we should probably go for 3×
 
 1. Migrate tokman to different toolchain, it's a small self-contained app, so it
    is easy to migrate to either Rust or Go that should leave smaller footprint.
-
    - Opened an issue for testing out running without Tokman deployment
      https://github.com/packit/tokman/issues/72
 

docs/deployment/specifics/packit-service.md

@@ -60,7 +60,6 @@ To make it work, you need to:
 - Since our infrastructure does not support shared volumes, we need to attach
   one volume with a cache to each worker and one to each corresponding sandbox
   pod.
-
   - In the case of workers, this is done during the deployment.
   - For sandboxes, there is an option in the service config (the environment
     variable needs to differ for each worker and is set during startup of the

docs/deployment/specifics/redict.md

@@ -8,7 +8,6 @@ We have tested a seamless migration from Redis to Redict on our production
 deployment. To reproduce:
 
 1. We have deployed Redict to our production cluster.
-
    - Defaults have been changed to:
 
      ```yaml
@@ -34,7 +33,6 @@ deployment. To reproduce:
 
 3. After the data exchange is done, change **all** references in variables to
    redis to point to the new hostname, in this case `redis → redict`.
-
    - Run
 
      ```