diff --git a/docs/features/techdocs/addons.md b/docs/features/techdocs/addons.md
index 831729d093..fe1058b2ca 100644
--- a/docs/features/techdocs/addons.md
+++ b/docs/features/techdocs/addons.md
@@ -52,6 +52,8 @@ Addons are rendered in the order in which they are registered.
 
 ## Installing and using Addons
 
+To start using Addons you need to add the `@backstage/plugin-techdocs-module-addons-contrib` package to your app. You can do that by running this command from the root of your project: `yarn add --cwd packages/app @backstage/plugin-techdocs-module-addons-contrib`
+
 Addons can be installed and configured in much the same way as extensions for
 other Backstage plugins: by adding them underneath an extension registry
 component (`<TechDocsAddons>`) under the route representing the TechDocs Reader
@@ -74,6 +76,18 @@ import { ReportIssue } from '@backstage/plugin-techdocs-module-addons-contrib';
 </Route>;
 ```
 
+If you are using a custom [TechDocs reader page](./how-to-guides.md#how-to-customize-the-techdocs-reader-page) your setup will be very similar, here's an example:
+
+```ts
+<Route path="/docs/:namespace/:kind/:name/*" element={<TechDocsReaderPage />}>
+  <TechDocsAddons>
+    <ReportIssue />
+    {/* Other addons can be added here. */}
+  </TechDocsAddons>
+  {techDocsPage} // This is your custom TechDocs reader page
+</Route>
+```
+
 The process for configuring Addons on the documentation tab on the entity page
 is very similar; instead of adding the `<TechDocsAddons>` registry under a
 `<Route>`, you'd add it as a child of `<EntityTechdocsContent />`: