Reword scope statements

Instead of "official plugins", we'd like to say "core features and
plugins". As to indicate, all the things that are part of a vanilla
install of Grafna.

CONTRIBUTING.md

@@ -10,10 +10,9 @@ participants to adhere to it.
 
 ## Plugin Scope
 
-**Grafonnet only aims to support official plugins.**
+**Grafonnet only aims to support core features and plugins.**
 
-We've drawn this line to ensure that the code base stays focused and manageable
-over time. We do, however, encourage development and use of community Grafonnet
-plugins. See the [Community
-Plugins](https://grafana.github.io/grafonnet-lib/community-plugins/) page for
-more info on this.
+While Grafonnet itself only supports core Grafana functionality, we strongly
+encourage development and use of community Grafonnet extensions. See the
+[Community Plugins](https://grafana.github.io/grafonnet-lib/community-plugins/)
+page for more info on this.

docs/community-plugins.md

@@ -1,7 +1,7 @@
 # Community Plugins
 
 Jsonnet makes it easy to patch an existing library. Although Grafonnet only
-supports core Grafana features, it is easy to extend. For example:
+supports core Grafana features and plugins, it is easy to extend. For example:
 
 ```jsonnet
 local grafonnet = (import 'grafonnet-lib/grafana.libsonnet')

docs/index.md

@@ -25,9 +25,9 @@ that would not be covered by Grafonnet already.
 
 Grafonnet aims to support any basic feature of dashboards (annotations,
 templates, rows, panels...) as well as a number of datasources and plugins. That
-is, official plugins only.
+is, core Grafana features and plugins only.
 
-We do, however, encourage development and use of community Grafonnet plugins.
+We do, however, encourage development and use of community Grafonnet extensions.
 See the [Community Plugins](community-plugins) page for more info on this.
 
 ## Code of Conduct