From d16bf7f5cdf61aacd75e9bbd24a305061264cfbe Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Tue, 8 Aug 2023 16:34:28 -0400
Subject: [PATCH] Fixed titling of note

---
 .../02_connecting_your_cluster/connecting_from_gcp/index.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx
index b2f4326d68e..6c5ad5c0dc4 100644
--- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx
+++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/connecting_from_gcp/index.mdx
@@ -87,7 +87,7 @@ In the Google Cloud project connected to BigAnimal, to provide access to your cl
    1. For **Name**, use the name of the Postgres cluster (`p-mckwlbakq5`).
 
    1. For **IPv4 range**, assign the CIDR for the field IPv4 range, for example, `10.247.214.0/29`.
-   !!! Note Recommendations for IP range
+   !!! Note "Recommendations for IP range"
        - Allocate at least 8 IP addresses to the CIDR. The subnet mask must not be greater than 29.
        - Avoid overlap with other reserved IP ranges by not allocating too many IP addresses at one time.
        - If you encounter the error "This IPv4 address range overlaps with a subnet you already added. Enter an address range that doesn't overlap.", use another CIDR block until no error is returned.