From dfca01e4693d316db9e4e210b401fa38add988cc Mon Sep 17 00:00:00 2001 From: Frieder Schlesier Date: Wed, 13 Nov 2019 00:34:04 +0100 Subject: [PATCH] fix typo in v1 to v2 migration guide --- docs/content/migration/v1-to-v2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/migration/v1-to-v2.md b/docs/content/migration/v1-to-v2.md index d98318e51..c56056d41 100644 --- a/docs/content/migration/v1-to-v2.md +++ b/docs/content/migration/v1-to-v2.md @@ -519,7 +519,7 @@ Use Case: Incoming requests to `http://company.org/admin` are forwarded to the w with the path `/admin` stripped, e.g. to `http://:/`. In this case, you must: * First, configure a router named `admin` with a rule matching at least the path prefix with the `PathPrefix` keyword, -* Then, define a middlware of type [`stripprefix`](../../middlewares/stripprefix/), which remove the prefix `/admin`, associated to the router `admin`. +* Then, define a middleware of type [`stripprefix`](../../middlewares/stripprefix/), which remove the prefix `/admin`, associated to the router `admin`. !!! example "Strip Path Prefix When Forwarding to Backend" @@ -974,7 +974,7 @@ You need to activate the API to access the [dashboard](../operations/dashboard.m As the dashboard access is now secured by default you can either: * define a [specific router](../operations/api.md#configuration) with the `api@internal` service and one authentication middleware like the following example -* or use the [unsecure](../operations/api.md#insecure) option of the API +* or use the [insecure](../operations/api.md#insecure) option of the API !!! info "Dashboard with k8s and dedicated router"