diff --git a/docs/bundle-add.md b/docs/bundle-add.md
index 0d365f65f..d297782bb 100644
--- a/docs/bundle-add.md
+++ b/docs/bundle-add.md
@@ -89,5 +89,5 @@ You can't use a `fleet.yaml` in resources, it is only used by the fleet-cli to c
 The `spec.targetRestrictions` field is not useful, as it is an allow list for targets specified in `spec.targets`. It is not needed, since `targets` are explicitly given in a bundle and an empty `targetRestrictions` defaults to allow.
 
 :::note
-You can use Fleet CLI to convert a Helm chart into a `bundle`. For more information, refer to [Convert a Helm chart into a bundle using CLI.](install-usage-fleetCLI.md#convert-a-helm-chart-into-a-bundle).
+You can use Fleet CLI to convert a Helm chart into a `bundle`. For more information, refer to [Convert a Helm chart into a bundle using CLI.](install-usage-fleet-cli.md#convert-a-helm-chart-into-a-bundle).
 :::
\ No newline at end of file
diff --git a/docs/install-usage-fleetCLI.md b/docs/install-usage-fleet-cli.md
similarity index 100%
rename from docs/install-usage-fleetCLI.md
rename to docs/install-usage-fleet-cli.md
diff --git a/docs/ref-bundle-stages.md b/docs/ref-bundle-stages.md
index 3bce7c6d7..2d5507a69 100644
--- a/docs/ref-bundle-stages.md
+++ b/docs/ref-bundle-stages.md
@@ -59,4 +59,4 @@ fleet target --bundle-file bundle.yaml --dump-input-list  > bd.yaml
 fleet deploy --input-file bd.yaml --dry-run
 ```
 
-For more information, refer to [Fleet CLI Key commands.](install-usage-fleetCLI.md#key-commands)
\ No newline at end of file
+For more information, refer to [Fleet CLI Key commands.](install-usage-fleet-cli.md#key-commands)
\ No newline at end of file
diff --git a/docs/ref-fleet-yaml.md b/docs/ref-fleet-yaml.md
index dc6813249..8b3e35f88 100644
--- a/docs/ref-fleet-yaml.md
+++ b/docs/ref-fleet-yaml.md
@@ -449,7 +449,7 @@ avoid conflicts with other templating languages.
 Note that if the functions output changes with every call, e.g. `uuidv4`, the
 bundle will get redeployed.
 
-You can [test values templating with the CLI](./install-usage-fleetCLI.md#key-commands) against existing clusters.
+You can [test values templating with the CLI](./install-usage-fleet-cli.md#key-commands) against existing clusters.
 
 The template context has the following keys:
 
diff --git a/docs/validate-fleetCLI.md b/docs/validate-fleet-cli.md
similarity index 99%
rename from docs/validate-fleetCLI.md
rename to docs/validate-fleet-cli.md
index 6fbe686cd..e7c9fdb34 100644
--- a/docs/validate-fleetCLI.md
+++ b/docs/validate-fleet-cli.md
@@ -21,7 +21,7 @@ You see the following fields:
 * `BUNDLEDEPLOYMENTS-READY` shows how many targets are ready out of the total.  
 * `STATUS` may show Ready, Modified, or other conditions based on the `rollout`.
 
-:::note:
+:::note
 If this field shows 1/1, the bundle is successfully deployed to one cluster.
 :::
 
diff --git a/sidebars.js b/sidebars.js
index f00a3e0f6..85a9bf41b 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -9,8 +9,8 @@ module.exports = {
       items:[
         'quickstart',
         'tut-deployment',
-        'install-usage-fleetCLI',
-        'validate-fleetCLI',
+        'install-usage-fleet-cli',
+        'validate-fleet-cli',
         {type:'doc', id:'uninstall'},
       ],
     },