diff --git a/docs/extending/create-plugin.mdx b/docs/extending/create-plugin.mdx
index 478b655f4..ad82039f1 100644
--- a/docs/extending/create-plugin.mdx
+++ b/docs/extending/create-plugin.mdx
@@ -5,6 +5,7 @@ title: Client Plugin API
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
+import {FbInternalOnly, OssOnly} from 'internaldocs-fb-helpers';
 
 ## FlipperPlugin
 
@@ -236,10 +237,26 @@ addPlugin({
 </TabItem>
 </Tabs>
 
-### Using the FlipperClient singleton to send data  
+### Using a plugin instance to send data
 
 It is often useful to get an instance of a Flipper plugin to send data to it. Flipper makes this simple with built-in support.
 
+<FbInternalOnly>
+
+#### Dependency Injection (Android only)
+
+The preferred method to obtain a plugin instance is to use dependency injection when available.
+For apps like fb4a that use dependency injection, a Module should have already been created by the create-plugin script.
+This module will define a Singleton instance of your plugin that gets added to the FlipperClient.
+
+You should use this instance of the plugin, by having it injected into your product code by the DI framework.
+Alternatively, you can modify the plugin's injection module so that it injects a component into the FlipperPlugin.
+
+
+</FbInternalOnly>
+
+#### using FlipperClient to obtain a plugin instance
+
 Plugins should be treated as singleton instances as there can only be one `FlipperClient` and each `FlipperClient` can only have one instance of a certain plugin. The Flipper API makes this simple by offering a way to get the current client and query it for plugins.
 
 Plugins are identified by the string that their identifier method returns, in this example, "MyFlipperPlugin". Note that null checks may be required as plugins may not be initialized, for example in production builds.
@@ -248,7 +265,7 @@ Plugins are identified by the string that their identifier method returns, in th
 <TabItem value="android">
 
 ```java
-final FlipperClient client = AndroidFlipperClient.getInstance(context);
+final FlipperClient client = AndroidFlipperClient.getInstanceIfInitialized(context);
 if (client != null) {
   final MyFlipperPlugin plugin = client.getPluginByClass(MyFlipperPlugin.class);
   plugin.sendData(myData);
diff --git a/docs/extending/send-data.mdx b/docs/extending/send-data.mdx
index 270e49482..bb469ab79 100644
--- a/docs/extending/send-data.mdx
+++ b/docs/extending/send-data.mdx
@@ -5,4 +5,4 @@ title: Providing Data to Plugins
 
 import {Redirect} from '@docusaurus/router';
 
-<Redirect to="/docs/extending/create-plugin#using-the-flipperclient-singleton-to-send-data" />
+<Redirect to="/docs/extending/create-plugin#using-a-plugin-instance-to-send-data" />
diff --git a/website/sidebars.js b/website/sidebars.js
index 966a87184..74c512da1 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -101,18 +101,6 @@ module.exports = {
       'extending/arch',
       'extending/client-plugin-lifecycle',
       'extending/layout-inspector',
-      ...fbInternalOnly([
-        {
-          Android: [
-            'fb/android-plugin-development-Android-interacting-0',
-          ],
-        },
-        {
-          iOS: [
-            'fb/ios-plugin-development-sending-data-to-an-ios-plugin-0',
-          ],
-        },
-      ]),
     ],
     Workflow: [
       'extending/js-setup',