fix: Run linkchecker in CI (#2209)

Author: untitaker

.github/workflows/test.yml

@@ -66,3 +66,27 @@ jobs:
       - run: yarn install
       - name: Run Tests
         run: yarn build:test
+
+  job_linkcheck:
+    name: Test (Linkchecker)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: volta-cli/action@v1
+      - uses: actions/cache@v2
+        with:
+          path: ${{ github.workspace }}/node_modules
+          key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
+      - run: yarn install
+      - run: yarn build
+      - name: Install linkcheck
+        run: |-
+          wget https://github.com/filiph/linkcheck/releases/download/v2.0.12/linkcheck-linux-x64.exe -O ./linkcheck
+          chmod +x ./linkcheck
+      - name: Install httpserver
+        run: volta install http-server
+      - name: Run linkcheck
+        run: |-
+          http-server public/ > /dev/null &
+          sleep 5
+          ./linkcheck

src/platforms/common/enriching-error-data/additional-data/index.mdx

@@ -33,15 +33,15 @@ If Sentry captures some predefined data but doesn’t expose it as a tag, you ca
 
 `level`
 
-: Defines the severity of an event. The level can be set to one of five values, which are, in order of severity: `fatal`, `error`, `warning`, `info`, and `debug.error`. Learn how to set the level in [Set the Level](#set-the-level)
+: Defines the severity of an event. The level can be set to one of five values, which are, in order of severity: `fatal`, `error`, `warning`, `info`, and `debug.error`. Learn how to set the level in [Set the Level](./set-level/)
 
 `user`
 
 : Providing user information to Sentry helps you evaluate the number of users affecting an issue and evaluate the quality of the application. Learn how to capture user information in Capture the User
 
 `fingerprint`
 
-: Sentry uses one or more fingerprints to determine how to group errors into issues. Learn more about Sentry's approach to grouping algorithms in [Grouping Events into Issues](/data-management/event-grouping/). Learn how to override the default group in very advanced use cases in [Modify the Default Fingerprint](#modify-the-default-fingerprint)
+: Sentry uses one or more fingerprints to determine how to group errors into issues. Learn more about Sentry's approach to grouping algorithms in [Grouping Events into Issues](../../data-management/event-grouping/). Learn how to override the default group in very advanced use cases in [Modify the Default Fingerprint](../../data-management/event-grouping/sdk-fingerprinting/)
 
 `environment`