From a1fbe711875562615dce77ee41da82ed26b8c379 Mon Sep 17 00:00:00 2001 From: Gidi Meir Morris Date: Tue, 17 Mar 2020 16:34:47 +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 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugins/alerting/README.md b/x-pack/plugins/alerting/README.md index 957fe34dd2f0c..84f4866af642a 100644 --- a/x-pack/plugins/alerting/README.md +++ b/x-pack/plugins/alerting/README.md @@ -272,7 +272,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 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. +In order for the Alerting framework to know that your plugin has its own internal view for displaying an alert, you must resigter a navigation handler within the framework. A navigation handler is nothing more than a function that receives an Alert and its corresponding AlertType, and is expected to then return the path *within your plugin* which knows how to display this alert.