From dd5b1151645f0701f11276e1bb842c2386cef138 Mon Sep 17 00:00:00 2001 From: Joseph Perez <45749060+josmperez@users.noreply.github.com> Date: Thu, 23 Feb 2023 10:29:34 -0800 Subject: [PATCH] Docs: Fix of typo and delete of unnecessary sentence in 'Sign a plugin' doc (#63538) * Typo fix, minor edit Signed-off-by: Joe Perez * Prettier fixes Signed-off-by: Joe Perez --------- Signed-off-by: Joe Perez --- docs/sources/developers/plugins/sign-a-plugin.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/sources/developers/plugins/sign-a-plugin.md b/docs/sources/developers/plugins/sign-a-plugin.md index 6f611214160..60785a347cc 100644 --- a/docs/sources/developers/plugins/sign-a-plugin.md +++ b/docs/sources/developers/plugins/sign-a-plugin.md @@ -12,9 +12,7 @@ Before you can sign your plugin, you need to decide whether you want to sign it If you want to make your plugin publicly available outside of your organization, you need to sign your plugin under a _community_ or _commercial_ [signature level](#plugin-signature-levels). Public plugins are available from [grafana.com/plugins](https://grafana.com/plugins) and can be installed by anyone. -For more information on how to install a public plugin, refer to [Install Grafana plugins]({{< relref "../../administration/plugin-management#install-a-plugin" >}}). - -If you intend to only use the plugin within your organization, you can to sign it under a _private_ [signature level](#plugin-signature-levels). +If you intend to only use the plugin within your organization, you can sign it under a _private_ [signature level](#plugin-signature-levels). ## Generate an API key