Merge pull request #263911 from vicancy/patch-11

Update docs

Author: prmerger-automator[bot]

articles/azure-signalr/signalr-quickstart-azure-functions-python.md

@@ -3,7 +3,7 @@ title: Azure SignalR Service serverless quickstart - Python
 description: A quickstart for using Azure SignalR Service and Azure Functions to create an App showing GitHub star count using Python.
 author: vicancy
 ms.author: lianwei
-ms.date: 12/15/2022
+ms.date: 01/23/2024
 ms.topic: quickstart
 ms.service: signalr
 ms.devlang: python
@@ -25,7 +25,7 @@ This quickstart can be run on macOS, Windows, or Linux.  You will need the follo
 | An Azure subscription |If you don't have an Azure subscription, create an [Azure free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)|
 | A code editor | You'll need a code editor such as [Visual Studio Code](https://code.visualstudio.com/). |
 | [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing)| Requires version 2.7.1505 or higher to run Python Azure Function apps locally.|
-| [Python 3.6+](https://www.python.org/downloads/)| Azure Functions requires Python 3.6+. See [Supported Python versions](../azure-functions/functions-reference-python.md#python-version). |
+| [Python 3.7+](https://www.python.org/downloads/)| Azure Functions requires Python 3.7+. See [Supported Python versions](../azure-functions/functions-reference-python.md#python-version). |
 | [Azurite](../storage/common/storage-use-azurite.md)| SignalR binding needs Azure Storage.  You can use a local storage emulator when a function is running locally. |
 | [Azure CLI](/cli/azure/install-azure-cli)| Optionally, you can use the Azure CLI to create an Azure SignalR Service instance. |
 

articles/azure-web-pubsub/includes/terms.md

@@ -3,12 +3,12 @@ author: vicancy
 ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.topic: include
-ms.date: 07/28/2022
+ms.date: 01/23/2024
 ---
 
 - **Connection**: A connection, also known as a client or a client connection, represents an individual WebSocket connection connected to the Web PubSub service. When successfully connected, a unique connection ID is assigned to this connection by the Web PubSub service.
 
-- **Hub**: A hub is a logical concept for a set of client connections. Usually you use one hub for one purpose, for example, a *chat* hub, or a *notification* hub. When a client connection connects, it connects to a hub, and during its lifetime it belongs to that hub. Once a client connection connects to the hub, the hub exists. Different applications can share one Azure Web PubSub service by using different hub names.
+- **Hub**: A hub is a logical concept for a set of client connections. Usually you use one hub for one scenario, for example, a *chat* hub, or a *notification* hub. When a client connection connects, it connects to a hub, and during its lifetime it belongs to that hub. Once a client connection connects to the hub, the hub exists. Different applications can share one Azure Web PubSub service by using different hub names. While there is no strict limit on the number of hubs, a **hub** consumes more service load comparing to a **group**. It is recommended to have a predetermined set of hubs rather than generating them dynamically.
 
 - **Group**: A group is a subset of connections to the hub. You can add a client connection to a group, or remove the client connection from the group, anytime you want. For example, when a client joins a chat room, or when a client leaves the chat room, this chat room can be considered to be a group. A client can join multiple groups, and a group can contain multiple clients. The group is like a group "session", the group session is created once someone joins the group, and the session is gone when no one is in the group. Messages sent to the group are delivered to all of the clients connected to the group.
 
@@ -24,4 +24,4 @@ ms.date: 07/28/2022
 
 - **Event Listener(preview)**: The event listener just listens to the client events but can't interfere the lifetime of your clients through their response. Details are described in [Event listener](..\concept-service-internals.md#event-listener) section.
 
-- **Server**: The server can handle client events, manage client connections, or publish messages to groups. Both event handler and event listener are considered to be server-side. Details about **server** are described in the [Server protocol](..\concept-service-internals.md#server-protocol) section.
+- **Server**: The server can handle client events, manage client connections, or publish messages to groups. Both event handler and event listener are considered to be server-side. Details about **server** are described in the [Server protocol](..\concept-service-internals.md#server-protocol) section.

articles/azure-web-pubsub/reference-client-sdk-python.md

@@ -1,12 +1,12 @@
 ---
 title: Reference - Python Client-side SDK for Azure Web PubSub
 description: This reference describes the Python client-side SDK for Azure Web PubSub service.
-author: kevinguo-ed
-ms.author: kevinguo
+author: vicancy
+ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.custom: devx-track-python
-ms.topic: conceptual 
-ms.date: 07/17/2023
+ms.topic: reference 
+ms.date: 01/23/2024
 ---
 
 # Azure Web PubSub client library for Python
@@ -27,7 +27,7 @@ As shown in the diagram, your clients establish WebSocket connections with your
 ## Getting started
 
 ### Prerequisites
-- [Python 3.7+](https://www.python.org/downloads/)
+- [Python 3.8+](https://www.python.org/downloads/)
 - An Azure subscription
 - A Web PubSub resource