diff --git a/features/plugins.mdx b/features/plugins.mdx
index 0c4446c..a8f3ee0 100644
--- a/features/plugins.mdx
+++ b/features/plugins.mdx
@@ -73,7 +73,9 @@ Registry plugins follow the app. After a TablePro update, each plugin installed
 - A plugin that is not loaded, such as one rejected after the update, installs and loads at once.
 - A plugin that is loaded downloads in the background and replaces the old one the next time TablePro starts. Its row in **Settings > Plugins** reads "Updates when TablePro restarts" until then.
 
-If the registry has no newer build yet, the check runs again after 30 seconds, 5 minutes, then every 10 minutes, five tries in all. Connecting to a database whose plugin is outdated checks again first. Bundled plugins update with the app, and a plugin installed from a file never updates from the registry.
+If the registry has no newer build yet, the check tries again in the background, on the schedule in [A plugin will not install or load](/troubleshooting#a-plugin-will-not-install-or-load). Connecting to a database whose plugin is outdated checks again first.
+
+Bundled plugins update with the app. A plugin installed from a file, including one installed over a registry plugin, updates from the registry only when an app update leaves it rejected and the registry has a compatible build of it.
 
 An app update can raise the plugin interface version. A plugin built for an older one is rejected at load instead of crashing, and stays in a banner in **Settings > Plugins** with the reason and an action until it is repaired: