docs: rendering plugin required for reporting (#21162)

* docs: rendering plugin required for reporting

* Update docs/sources/features/reporting.md

Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

docs/sources/administration/image_rendering.md

@@ -125,7 +125,7 @@ Please note that PhantomJS binaries are not included for ARM. To support this yo
 
 ## Alerting and render limits
 
-Alert notifications can include images, but rendering many images at the same time can overload the server where the renderer is running. For instructions of how to configure this, see [concurrent_render_limit](/installation/configuration/#concurrent-render-limit).
+Alert notifications can include images, but rendering many images at the same time can overload the server where the renderer is running. For instructions of how to configure this, see [concurrent_render_limit]({{< relref "../installation/configuration/#concurrent_render_limit" >}}).
 
 ## Troubleshooting
 

docs/sources/features/reporting.md

@@ -27,7 +27,12 @@ With Reports there are a few things to keep in mind, most importantly, any chang
 
 > SMTP must be configured for reports to be sent
 
-We recommend using the new image rendering plugin with reporting as it supports a wider range of panels than the built-in image rendering. Read more about it [here]({{< relref "../administration/image_rendering.md#grafana-image-renderer-plugin" >}})
+
+### Rendering
+
+> Reporting requires the [rendering plugin]({{< relref "../administration/image_rendering.md#grafana-image-renderer-plugin" >}}).
+
+Reporting with the built-in image rendering is not supported. We recommend installing the image renderer plugin.
 
 ## Usage