From 8cc2e8442635599eb899cd54411e3b5ea3f2f007 Mon Sep 17 00:00:00 2001 From: Gidi Meir Morris Date: Tue, 17 Mar 2020 16:34:34 +0000 Subject: [PATCH] typo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Mike Côté --- x-pack/plugins/alerting/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/x-pack/plugins/alerting/README.md b/x-pack/plugins/alerting/README.md index ef1f2e7760b1e..957fe34dd2f0c 100644 --- a/x-pack/plugins/alerting/README.md +++ b/x-pack/plugins/alerting/README.md @@ -270,7 +270,7 @@ server.newPlatform.setup.plugins.alerting.registerType({ ``` ## Alert Navigation -When registering an Alert Type, you'll likely want to provide a way of viewing alerts of that type within your own plugin, or perhaps you want to provide a view for all alerts created fro mwithin your solution within your own UI. +When registering an Alert Type, you'll likely want to provide a way of viewing alerts of that type within your own plugin, or perhaps you want to provide a view for all alerts created from within your solution within your own UI. In order for the Alerting framework to know that your plugin has its own interna; view for displaying an alert, you must resigter a navigation handler within the framework. @@ -536,4 +536,3 @@ The templating system will take the alert and alert type as described above and ``` There are limitations that we are aware of using only templates, and we are gathering feedback and use cases for these. (for example passing an array of strings to an action). -