diff --git a/modules/troubleshooting-cc-false-positives.adoc b/modules/troubleshooting-cc-false-positives.adoc
new file mode 100644
index 000000000000..98254011e941
--- /dev/null
+++ b/modules/troubleshooting-cc-false-positives.adoc
@@ -0,0 +1,14 @@
+:_mod-docs-content-type: PROCEDURE
+[id="troubleshooting-cc-false-positives_{context}"]
+= Troubleshooting false positives for missing resources
+
+[role="_abstract"]
+The plugin might report a missing resource even though the cluster custom resource (CR) is present in the cluster.
+
+.Procedure
+
+. Ensure you are using the latest version of the `cluster-compare` plugin. For more information, see "Installing the cluster-compare plugin".
+
+. Ensure you are using the most up-to-date version of the reference configuration.
+
+. Ensure that template has the same `apiVersion`, `kind`, `name`, and `namespace` fields as the cluster CR.
diff --git a/modules/troubleshooting-cc-multiple-matches.adoc b/modules/troubleshooting-cc-multiple-matches.adoc
new file mode 100644
index 000000000000..f0cddd1787ea
--- /dev/null
+++ b/modules/troubleshooting-cc-multiple-matches.adoc
@@ -0,0 +1,12 @@
+:_mod-docs-content-type: PROCEDURE
+[id="troubleshooting-cc-multiple-matches_{context}"]
+= Troubleshooting multiple template matches for the same CR
+
+[role="_abstract"]
+In some cases, more than one cluster CR can match a template because they feature the same `apiVersion`, `namespace`, and `kind`. The plugin's default matching compares the CR that features the least differences. You can optionally configure your reference configuration to avoid this situation.
+
+.Procedure
+
+. Ensure the templates feature distinct `apiVersion`, `namespace`, and `kind` values to ensure no duplicate template matching.
+
+. Use a user configuration file to manually match a template to a CR. For more information, see "Configuring manual matching between CRs and templates".