diff --git a/docs/core/integration-quality-scale/rules/discovery.md b/docs/core/integration-quality-scale/rules/discovery.md
index fae698fa5b0..b0d03a3fc3e 100644
--- a/docs/core/integration-quality-scale/rules/discovery.md
+++ b/docs/core/integration-quality-scale/rules/discovery.md
@@ -13,13 +13,13 @@ import RelatedRules from './_includes/related_rules.jsx'
A lot of devices have the ability to be discovered.
This can happen using one of the following methods:
- App (formerly known as add-ons)
-- Bluetooth
-- DHCP
-- HomeKit
-- mDNS
-- MQTT
-- SSDP
-- USB
+- [Bluetooth](/docs/creating_integration_manifest#bluetooth)
+- [DHCP](/docs/creating_integration_manifest#dhcp)
+- [HomeKit](/docs/creating_integration_manifest#homekit)
+- [mDNS](/docs/creating_integration_manifest#zeroconf)
+- [MQTT](/docs/creating_integration_manifest#mqtt)
+- [SSDP](/docs/creating_integration_manifest#ssdp)
+- [USB](/docs/creating_integration_manifest#usb)
This is a great way to make it easier for users to find and set up devices, since they don't have to manually look up which integration to use and then enter the host.
This greatly reduces the effort required to set up a device and thus improves the user experience.
@@ -115,6 +115,7 @@ class MyConfigFlow(ConfigFlow, domain=DOMAIN):
To learn more information about config flows, checkout the [config flow documentation](/docs/config_entries_config_flow_handler).
To learn more about discovery on network protocols, checkout the [Networking and discovery documentation](/docs/network_discovery).
To learn more about discovery for bluetooth devices, checkout the [Bluetooth documentation](/docs/bluetooth).
+To learn more about specifying different discovery methods in your manifest checkout the [Integration Manifest Documentation](/docs/creating_integration_manifest).
## Exceptions
@@ -123,4 +124,4 @@ Integrations where the devices can't be discovered are exempt from this rule.
## Related rules
-
\ No newline at end of file
+