diff --git a/.github/.linkspector.yml b/.github/.linkspector.yml
index 3ee6f587..09c265f2 100644
--- a/.github/.linkspector.yml
+++ b/.github/.linkspector.yml
@@ -1,4 +1,4 @@
 dirs:
-  - ../content/
+  - ./content/
 
-useGitIgnore: true
\ No newline at end of file
+useGitIgnore: true
diff --git a/.github/workflows/PR.yaml b/.github/workflows/PR.yaml
index 24f8f926..b3540fe9 100644
--- a/.github/workflows/PR.yaml
+++ b/.github/workflows/PR.yaml
@@ -15,7 +15,6 @@ jobs:
       - name: Run linkspector
         uses: umbrelladocs/action-linkspector@v1
         with:
-          github_token: ${{ secrets.PAT_CI_BOUNDLESS }}
-          reporter: local
+          reporter: github-pr-check
           fail_on_error: true
           config_file: .github/.linkspector.yml
diff --git a/content/docs/setup/README.md b/content/docs/setup/README.md
index ed07f06b..60920c7f 100644
--- a/content/docs/setup/README.md
+++ b/content/docs/setup/README.md
@@ -4,8 +4,7 @@
   [Releases](https://github.com/MirantisContainers/mke/releases) page of the MKE 4 repository.
 
 `mkectl` is supposed to be a single binary capable of managing MKE 4 clusters without any additional dependencies.
-However, as of version `0.0.5`, it still requires the following tools to be installed on your system:
+However, as of commit `e19af33`, it still requires the following tools to be installed on your system:
 
 - `kubectl` of version `1.29.0` or above ([download](https://kubernetes.io/docs/tasks/tools/#kubectl))
 - `k0sctl` of version `0.17.0` or above ([download](https://github.com/k0sproject/k0sctl/releases))
-- `bctl` of version `1.0.0-rc.1` or above ([download](https://github.com/MirantisContainers/boundless-cli/releases))
diff --git a/content/docs/setup/upgrade-from-mke-3/README.md b/content/docs/setup/upgrade-from-mke-3/README.md
index b9a7b24f..9ce9b8b5 100644
--- a/content/docs/setup/upgrade-from-mke-3/README.md
+++ b/content/docs/setup/upgrade-from-mke-3/README.md
@@ -60,6 +60,7 @@ Users can upgrade from MKE 3 to MKE 4 using the `mkectl` tool. The `mkectl` tool
 - Migrate manager nodes to k0s.
 - Migrate worker nodes to k0s.
 - Perform post upgrade cleanup to remove MKE 3 components.
+- Output the new MKE 4 config file.
 
 To upgrade an MKE 3 cluster, run the following command:
 
@@ -67,6 +68,10 @@ To upgrade an MKE 3 cluster, run the following command:
 mkectl upgrade --hosts-path <path-to-hosts-yaml> --admin-username <admin-username> --admin-password <admin-password>
 ```
 
+> If you don't specify `--config-out` flag, the MKE 4 config file will be printed to the console 
+after the migration is complete. You can save this output to a file for future use with `mkectl apply`.
+<br>Alternatively, you can set `--config-out` to the path where you want to save the MKE 4 config file.
+
 - The upgrade process will take some time to complete. After the upgrade is complete, verify that the MKE 4 cluster is running:
 
 ```shell
diff --git a/content/releases/README.md b/content/releases/README.md
index 78dbac29..e0154d4d 100644
--- a/content/releases/README.md
+++ b/content/releases/README.md
@@ -4,7 +4,9 @@
 
 
 ### Setup
-[Fresh Install](../docs/setup/install/README.md)
+[Install mkectl](../docs/setup/README.md)
+
+[Install MKE 4](../docs/setup/getting-started/README.md)
 
 [Upgrade from MKE 3](../docs/setup/upgrade-from-mke-3/README.md)