+
diff --git a/gatsby-node.js b/gatsby-node.js
index 0d404be13e2..cd27d09b8bc 100644
--- a/gatsby-node.js
+++ b/gatsby-node.js
@@ -426,6 +426,8 @@ exports.createSchemaCustomization = ({ actions }) => {
legacyRedirects: [String]
legacyRedirectsGenerated: [String]
showInteractiveBadge: Boolean
+ hideVersion: Boolean
+ displayBanner: String
}
enum TileModes {
diff --git a/product_docs/docs/edbcloud/beta/getting_started/01_check_resource_limits.mdx b/product_docs/docs/edbcloud/beta/getting_started/01_check_resource_limits.mdx
index 3a4653f6700..14582db830a 100644
--- a/product_docs/docs/edbcloud/beta/getting_started/01_check_resource_limits.mdx
+++ b/product_docs/docs/edbcloud/beta/getting_started/01_check_resource_limits.mdx
@@ -2,14 +2,24 @@
title: Raising Azure Resource Limits
---
-By default, Azure sets a very low limit on the number of Virtual Machines and Cores per region and on the number of Public IP Addresses per region that are available in a given subscription.
+By default, Azure sets a very low limit on the number of virtual machines and cores per region and on the number of Public IP Addresses per region that are available in a given subscription.
-The default number of total cores per subscription per region is 20. See [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager) for more information. You need to increase the total cores to account for the total number of cores you expect to use in each region and reserve these cores to be used by EDB. As an example, if you provision the largest virtual machine with high availability this would be 192 cores per region. EDB uses eight DSv2 virtual machine cores for managing your environment.
+The default number of total cores per subscription per region is 20. See [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager) for more information. You need to increase the total cores to account for the total number of cores you expect to use in each region and reserve these cores to be used by EDB. See the next section [Virtual Machine Quota Requirements](#virtual-machine-quota-requirements)for more information.
The default Public IP address limits for Public IP Addresses Basic and Public IP Addresses Standards is set to 10. See [Public IP address limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#publicip-address) for more information. You need to increase the limit of `Public IP Addresses - Basic` and `Public IP Addresses - Standard` for the regions where you plan to deploy your EDB clusters with the total number of EDB clusters you plan to use.
+## Virtual Machine Quota Requirements
+In each region, EDB Cloud uses six ESv3 and six DSv2 virtual machine cores to manage your EDB Cloud infrastructure.
+Your Postgres clusters deployed in the region use separate ESv3 virtual machine cores.
+The number of cores depends on the Instance Type and High Availability options of the clusters you provision. You can calculate the number of ESv3 cores required for your cluster based on the following:
-# Checking Current Utilization
+* Virtual machine instance of type E{N}Sv3 uses {N} cores. For example, an instance of type E64Sv3 uses 64 ESv3 cores.
+* Cluster running on an E{N}Sv3 instance with high availability not enabled uses exactly {N} ESv3 cores.
+* Cluster running on an E{N}Sv3 instance with high availability enabled uses 3 * {N} ESv3 cores.
+
+As an example, if you provision the largest virtual machine E64Sv3 with high availability enabled, it requires (3 * 64)=192 ESv3 cores per region. EDB Cloud infrastructure requires an additional six ESv3 and six DSv2 virtual machine cores per region.
+
+## Checking Current Utilization
To check if you have adequate Azure resources to provision new clusters:
@@ -21,16 +31,16 @@ To check if you have adequate Azure resources to provision new clusters:
6. Search for Public IP to view networks limits.
-# Increasing Network Quota
+## Increasing Network Quota
-You can increase the number of public IP addresses for your account either by using Azure's portal if you have appropriate privileges or by submitting a support request. See:
+You can increase the number of public IP addresses for your account either by using Azure's portal if you have appropriate privileges or by submitting a support request. See:
- [Request Networking quota increase at subscription level using Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-help--support)
- [Request networking quota increase at subscription level using Usages + quotas](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-usages--quotas)
-# Increasing Virtual Machine Quota
+## Increasing Virtual Machine Quota
You can increase the number of ESv3 Series virtual machines per region for your account either by using Azure's portal if you have appropriate privileges or by submitting a support request. See:
diff --git a/src/components/logo.js b/src/components/logo.js
index a6c40e3f624..e453f7baa1a 100644
--- a/src/components/logo.js
+++ b/src/components/logo.js
@@ -1,5 +1,5 @@
import React from "react";
-import LogoSvg from "../../static/images/edb-docs-logo-disc-dark-beta.svg";
+import LogoSvg from "../../static/icons/edb-docs-logo-disc-dark.svg";
function Logo({ className, width, height }) {
return