From 7d3079a3f2dd7461f55fc6a76cefb8093850efff Mon Sep 17 00:00:00 2001 From: Michael Quigley Date: Thu, 25 Jul 2024 11:45:39 -0400 Subject: [PATCH] docs (#704) --- docs/guides/self-hosting/interstitial-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/self-hosting/interstitial-page.md b/docs/guides/self-hosting/interstitial-page.md index a32a04f3..217bc079 100644 --- a/docs/guides/self-hosting/interstitial-page.md +++ b/docs/guides/self-hosting/interstitial-page.md @@ -10,7 +10,7 @@ Interstitial pages can be enabled on a per-frontend basis. This allows the inter The interstitial page requirement can also be overridden on a per-account basis, allowing shares created by specific accounts to bypass the interstitial requirement on frontends that enable it. This facilitates building infrastructure that grants trusted users additional privileges. -By default, if you do not specifically enable interstitial pages, then your self-hosted service instance will not offer them. +By default, if you do not specifically enable interstitial pages on a public frontend, then your self-hosted service instance will not offer them. Let's take a look at how the interstitial pages mechanism works. The following diagram shows the share configuration rendezvous made between the zrok controller and a zrok frontend: