Link adjustments

Author: AnneLaure1307

.github/workflows/misc.sync.yaml

@@ -0,0 +1,26 @@
+name: misc.sync
+on:
+  # Run manually a sync between current repo / develop and public repo develop
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+jobs:
+  sync:
+    permissions:
+      actions: read
+      contents: write
+    runs-on:
+      - ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Push to public Docs repo
+        env:
+          PUBLIC_ORG_NAME: strangebeecorp
+          PRIVATE_ORG_NAME: strangebee
+        run: |
+          git config --global user.email "jordan.zedi@strangebee.com"
+          git config --global user.name "Jordan ZEDI"
+          git remote add private_docs_repo https:///${{ env.PUBLIC_ORG_NAME }}:${{ secrets.PUBLIC_DOCS_TOKEN }}@github.com/${{ env.PUBLIC_ORG_NAME }}/docs
+          git push --force private_docs_repo main

docs/thehive/operations/configure-audit-logs-storage-elasticsearch.md

@@ -6,7 +6,7 @@ By default, TheHive stores audit logs in Apache Cassandra via JanusGraph. Howeve
 
 This topic provides step-by-step instructions for configuring TheHive's audit log storage in Elasticsearch for existing instances, including the option to migrate historical logs from JanusGraph.
 
-For new installations, refer to the [Step-by-Step Guide](../installation/step-by-step-installation-guide.md#fontawesome-solid-list-elasticsearch) for instructions.
+For new installations, refer to the [Step-by-Step Guide](../installation/step-by-step-installation-guide.md) for instructions.
 
 !!! info "Reasons to consider Elasticsearch"
     Elasticsearch is better suited for managing large volumes of audit logs. It enhances performance by efficiently handling data, reducing latency, and offering advanced search capabilities. If your organization generates a significant amount of audit logs, migrating to Elasticsearch can improve both data management and retrieval.