From 5ec891a5fc67abbd4be8e3c827153799aa1741b4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Joe=20G=C3=B6rlich?=
 <37544323+joegoerlich@users.noreply.github.com>
Date: Wed, 18 Jun 2025 13:22:40 +0200
Subject: [PATCH] Update configure-access-control-http-e7d4927.md

added an example for a protocol upgrade
---
 .../configure-access-control-http-e7d4927.md                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/1-connectivity-documentation/configure-access-control-http-e7d4927.md b/docs/1-connectivity-documentation/configure-access-control-http-e7d4927.md
index 04a5d6e..4550ad0 100644
--- a/docs/1-connectivity-documentation/configure-access-control-http-e7d4927.md
+++ b/docs/1-connectivity-documentation/configure-access-control-http-e7d4927.md
@@ -162,7 +162,7 @@ The Cloud Connector checks that the path part of the URL \(up to but not includi
 
 The *Active* checkbox lets you specify, if that resource is initially enabled or disabled. See the section below for more information on enabled and disabled resources.
 
-The *Upgrade Allowed* checkbox lets you specify, whether that resource allows a protocol upgrade.
+The *Upgrade Allowed* checkbox lets you specify, whether that resource allows a protocol upgrade, for example, upgrade a HTTPS connection to a WebSocket connection.
 
 Back to [Tasks](configure-access-control-http-e7d4927.md#loioe7d4927dbb571014af7ef6ebd6cc3511__content)