message: Update docs about `monitoring-path`
  Removed a note that was a copy from `monitoring_urls` and didn't apply to the section.
diff: @@ -230,9 +230,6 @@ In the `"www.example.com"` example repeated below, we see two more options \(als
  ### **Monitoring a specific path**
  -!!! Note "Note:"
  - Please note, Lagoon does not provide any direct integration to a monitoring service, this just adds the URLs to the API. On amazee.io, we take the `monitoring_urls` and add them to our StatusCake account.
  -
  When [UptimeRobot](https://uptimerobot.com/) is configured for your cluster \(OpenShift or Kubernetes\), Lagoon will inject annotations to each route/ingress for use by the `stakater/IngressControllerMonitor`. The default action is to monitor the homepage of the route. If you have a specific route to be monitored, this can be overridden by adding a `monitoring-path` to your route specification. A common use is to set up a path for monitoring which bypasses caching to give a more real-time monitoring of your site.
  ```yaml title=".lagoon.yml"
  