From 07b66c67d2a2ebc88e218136207480a07ef2eb62 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stig=20Kleppe-J=C3=B8rgensen?= Date: Sat, 10 Feb 2018 11:11:00 +0100 Subject: [PATCH] Spelling fixes --- docs/securing-unleash.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/securing-unleash.md b/docs/securing-unleash.md index d7d2b6c735..137aace218 100644 --- a/docs/securing-unleash.md +++ b/docs/securing-unleash.md @@ -22,7 +22,7 @@ unleash.start({ }); ``` -Additionally, you can trigger the admin interfact to prompt the user to sign in by configuring your middleware to return a `401` status on +Additionally, you can trigger the admin interface to prompt the user to sign in by configuring your middleware to return a `401` status on protected routes. The response body must contain a `message` and a `path` used to redirect the user to the proper login route. ```json @@ -79,4 +79,4 @@ unleash.start({ [client-auth-unleash.js](https://github.com/Unleash/unleash/blob/master/examples/client-auth-unleash.js) -PS! Remember to disable legacy route with by setting the `enableLegacyRoutes` option to false. This will require all your clients to be on v3.x. +PS! Remember to disable legacy route by setting the `enableLegacyRoutes` option to false. This will require all your clients to be on v3.x.