pac plugin commands don't belong here

Author: JimDaly

powerapps-docs/developer/component-framework/import-custom-controls.md

@@ -103,37 +103,6 @@ To use the `push` capability, do the following:
    > [!NOTE]
    > The publisher prefix that you use with the `push` command should match the publisher prefix of your solution in which the components will be included.
 
-## Create a plug-in project and add a reference to it in your solution
-
-> [!NOTE]
-> The plugin command is in public preview and 
-Microsoft Power Platform CLI now supports creating a plug-in project and packaging it in a solution by adding a reference to the plug-in project. The [pac plugin init](/power-platform/developer/cli/reference/plugin) command creates the template files (csproj, Plugin.cs & ServiceHelper.cs) in the directory. To do so: 
-
-1. Ensure that you have a valid authentication profile created.
-2. Navigate to the root directory where you want the project to be created.
-3. Run the [pac auth create](/power-platform/developer/cli/reference/auth) command:
-
-   ```CLI
-   pac auth create –url <https://xyz.crm.dynamics.com>
-   ```
-4. Run the [pac plugin init](/power-platform/developer/cli/reference/plugin) command to create the plug-in project
-
-   ```CLI
-   pac plugin init
-   ```
-
-5. Add a reference to your solution project  using the [pac solution add-reference](/power-platform/developer/cli/reference/solution) command so that the plug-in project gets built when the solution is built.
-
-   ```CLI
-   pac solution add-reference –path <path to your plugin project>
-   ```
-
-6. Run the command to build the solution and the referenced plug-in.
-
-   ```CLI
-   msbuild
-   ```
-
 ## Remove components from a solution
 
 If you want to remove a code component from a solution file: