minor fixes

.github/workflows/get_context.yml

@@ -33,7 +33,7 @@ jobs:
           path: artifacts
       - name: Get Directory structure
         run: ls -lR
-      - run: python find_posts.py --lock-hours=0 --access-token=${{ secrets.ACCESS_TOKEN }} -c=./config.json
+      - run: python find_posts.py --lock-hours=0 --access-token=${{ secrets.ACCESS_TOKEN }} -c=config.json
       - name: Upload artifacts
         uses: actions/upload-artifact@v3
         with:

README.md

@@ -73,6 +73,7 @@ When using a cronjob, we are using file based locking to avoid multiple overlapp
 If you are running FediFetcher locally, my recommendation is to run it manually once, before turning on the cron job: The first run will be significantly slower than subsequent runs, and that will help you prevent overlapping during that first run.
 
 > **Note**
+> 
 > If you wish to run FediFetcher using Windows Task Scheduler, you can rename the script to the `.pyw` extension instead of `.py`, and it will run silently, without opening a console window.
 
 ### 2.3) Run FediFetcher from a container
@@ -105,6 +106,7 @@ FediFetcher has quite a few configuration options, so here is my quick configura
 If you configure FediFetcher this way, it'll fetch missing remote replies to the last 200 posts in your home timeline. It'll additionally backfill profiles of the last 80 people you followed, and of every account who appeared in your notifications during the past hour.
 
 > **Warning**
+> 
 > **Do NOT** include your `access-token` in the `config.json` when running FediFetcher as GitHub Action. When running FediFetcher as GitHub Action **ALWAYS** [set the Access Token as an Action Secret](#21-configure-and-run-the-github-action).
 
 #### Advanced Options