Release/2021 11 1 (#1984)

* initial import and style guide changes through the first example

initial import and style guide changes through the first example

* Cleaning up text in the private networking topic

* Cleaning text

* consolidated pros and cons

Moved the consolidated pros and cons to the Connect from External Azure Resources section

* Cleaning up the text and defining the structure for the steps.

* updated intro to examples

updated intro to examples
trying out adding a header for the examples and just using bold for the high level steps

* Attempting to merge with Dee Dee's updates

* Cleaning Text

* implemented structural changes - minor edits

Added a section to the Connecting to Your Cluster topic
Created separate topics for the two main approaches
Changed heading levels and added an intro to the walkthrough and links to the walkthrough for the first solution

* Addes screenshots.

Cleaned the low-level steps.

Added screenshots.

Added missing steps.

* more restructuring

more restructuring

* Reviewed and updated the content in the private networking pages

* edits and comparison table

Did some random cleanup
Took a pass at the On-premises topic
Created a draft of a Pros and Cons table

* Dee Dee's final edits prior to review

Updated the topic intro to mention private networking and other small edits

* last set of changes before the review

last set of changes before the review

* more reviewer notes

* Move private_networking to cluster_networking

* cluster networking whitespace cleanup

* make cluster_networking more abstract and pub/priv

* hack private endpoint example

* clean up code examples in vnet_vnet

* fixup connecting-from-azure

* Update product_docs/docs/edbcloud/beta/getting_started/creating_a_cluster/01_cluster_networking.mdx

* Update product_docs/docs/edbcloud/beta/getting_started/creating_a_cluster/01_cluster_networking.mdx

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/index.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* addressed a few of Ben's comments

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Addressing comments from Zane and Ben

* Addressing comments

* Addressed comments, regarding terminology and several other changes.

* Updated screenshot. Addressed comments.

* Added the content for monitoring Postgres instance on Azure using PEM

Added the content for monitoring Postgres instance on Azure using PEM

* Updated the content referencing EDB Cloud

Updated the content referencing EDB Cloud

* Update 03a_pem_define_azure_instance_connection.mdx

Missing "account".

* Update 03a_pem_define_azure_instance_connection.mdx

* added PEM monitoring content to Cloud doc

* Updated the Remote Monitoring of EDB Cloud content as per the inputs from DeeDee, Kelly and Anthony.

Updated the Remote Monitoring of EDB Cloud content as per the inputs from DeeDee, Kelly and Anthony.

* cleaning up after merging develop

resolved conflicts
made a few minor edits
updating case of headings

* Updated the content as per the dicussion with Dee Dee

Updated the content as per the dicussion with Dee Dee

* Updated the content as per dicussion with Anthony and Dee Dee.

Updated the content as per dicussion with Anthony and Dee Dee.

* fixed link

plus one minor edit

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* incorporating new comments

* Update product_docs/docs/edbcloud/beta/using_cluster/connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

Co-authored-by: Benjamin Anderson <[email protected]>

* Changing the positioning of the PEM solution per Adam

* Incorporated inputs from Zane

* minor edits

* redid rebranding changes

* removed video link

* more rebranding

* Added the content for monitoring Postgres instance on Azure using PEM

Added the content for monitoring Postgres instance on Azure using PEM

* Updated the content referencing EDB Cloud

Updated the content referencing EDB Cloud

* Update 03a_pem_define_azure_instance_connection.mdx

Missing "account".

* Update 03a_pem_define_azure_instance_connection.mdx

* added PEM monitoring content to Cloud doc

* Updated the Remote Monitoring of EDB Cloud content as per the inputs from DeeDee, Kelly and Anthony.

Updated the Remote Monitoring of EDB Cloud content as per the inputs from DeeDee, Kelly and Anthony.

* Updated the content as per the dicussion with Dee Dee

Updated the content as per the dicussion with Dee Dee

* Updated the content as per dicussion with Anthony and Dee Dee.

Updated the content as per dicussion with Anthony and Dee Dee.

* fixed link

plus one minor edit

* rebranding changes

* fixed label

* One copy-paste too many

Co-authored-by: Moiz Nalwalla <[email protected]>
Co-authored-by: Francisco González <[email protected]>
Co-authored-by: Benjamin Anderson <[email protected]>
Co-authored-by: Benjamin Anderson <[email protected]>
Co-authored-by: moiznalwalla <[email protected]>
Co-authored-by: nidhibhammar <[email protected]>
Co-authored-by: Anthony Waite <[email protected]>
Co-authored-by: Jon Ericson <[email protected]>

gatsby-config.js

@@ -20,7 +20,7 @@ const sourceToPluginConfig = {
   bart: { name: "bart", path: "product_docs/docs/bart" },
   bdr: { name: "bdr", path: "product_docs/docs/bdr" },
   harp: { name: "harp", path: "product_docs/docs/harp" },
-  edbcloud: { name: "edbcloud", path: "product_docs/docs/edbcloud" },
+  biganimal: { name: "biganimal", path: "product_docs/docs/biganimal" },
   efm: { name: "efm", path: "product_docs/docs/efm" },
   epas: { name: "epas", path: "product_docs/docs/epas" },
   eprs: { name: "eprs", path: "product_docs/docs/eprs" },

product_docs/docs/edbcloud/beta/getting_started/01_check_resource_limits.mdx → product_docs/docs/biganimal/release/getting_started/01_check_resource_limits.mdx

@@ -8,18 +8,17 @@ The default number of total cores per subscription per region is 20. See [Virtua
 
 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.
 
-<iframe width="560" height="315" src="https://www.youtube.com/embed/cfl11ajrPhE" title="Video walkthrough of raising Azure resource limits" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
 ## Virtual machine quota requirements
-In each region, EDB Cloud uses six ESv3 and six DSv2 virtual machine cores to manage your EDB Cloud infrastructure.
+In each region, BigAnimal uses six ESv3 and six DSv2 virtual machine cores to manage your BigAnimal 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:
 
 * 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.
+As an example, if you provision the largest virtual machine E64Sv3 with high availability enabled, it requires (3 * 64)=192 ESv3 cores per region. BigAnimal infrastructure requires an additional six ESv3 and six DSv2 virtual machine cores per region.
 
 ## Checking current utilization
 

product_docs/docs/biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx

@@ -0,0 +1,63 @@
+---
+title: Cluster networking architecture
+---
+
+BigAnimal clusters can be exposed to client applications in two ways:
+- Public - where the cluster is available on the Internet, and
+- Private - where access to the cluster is restricted to specific
+sources and network traffic never leaves the Azure network.
+
+## Basic architecture
+
+When you create your first cluster in a region, BigAnimal deploys a
+dedicated virtual network (VNet) in Azure to host all clusters and
+supporting management services.
+
+This VNet is named after the region where the cluster is deployed. 
+For example, if the cluster is deployed in the East US region, it is
+named `vnet-eastus`. This VNet uses IP addresses in the
+`10.240.0.0.16` space.
+
+## Public cluster load balancing
+
+When a cluster is created with public network access, an Azure
+Standard SKU Load Balancer is created and configured with a public IP
+address that always routes to the leader of your cluster. Once
+assigned, this IP address does not change unless you change the
+networking configuration for your cluster.
+
+Only one Azure Load Balancer is typically deployed in your Azure
+subscription per BigAnimal region; subsequent public clusters add
+additional IP addresses to the existing load balancer.
+
+## Private cluster load balancing
+
+When a cluster is created with public network access, an Azure
+Standard SKU Load Balancer is created and configured with an IP
+address that always routes to the leader of your cluster. Once
+assigned, this IP address does not change unless you change the
+networking configuration for your cluster.
+
+This IP address is private to the VNet hosting your BigAnimal
+services; by default it is not routable from other networks, even in
+your Azure account. See [Setting up Azure infrastructure to connect to a private network cluster](../../using_cluster/connecting_your_cluster/#setting-up-azure-infrastructure-to-connect-to-a-private-network-cluster) for details and instructions
+on how to properly configure routing for private clusters.
+
+Only one Azure Internal Load Balancer is typically deployed in your
+Azure subscription per BigAnimal region; subsequent private clusters add additional IP addresses to the existing load balancer.
+
+## DNS
+
+Every BigAnimal cluster, regardless of public or private networking
+status, is assigned a single DNS zone that maps to its exposed IP
+address, either public or private. When toggling between public and
+private, wait up to 120 seconds for DNS caches to flush.
+
+## Toggling between public and private
+
+Clusters can be changed from public to private and vice versa at any
+time. When this happens, the IP address previously assigned to the
+cluster is de-allocated, a new one is assigned, and DNS is updated
+accordingly.
+
+

product_docs/docs/edbcloud/beta/getting_started/03_create_cluster.mdx → product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx

@@ -1,6 +1,11 @@
 ---
 title: "Creating a cluster"
+
+redirects:
+  #adding hierarchy to the structure (Creating a Cluster topic nows has a child topic) so created a folder and moved the contents from 03_create_cluster to index.mdx
+  - ../03_create_cluster/
 ---
+
 !!! Note
 Prior to creating your cluster, make sure you have adequate Azure resources or your request to create a cluster will fail. See [Raising your Azure resource limits](01_check_resource_limits).
 !!!
@@ -44,8 +49,8 @@ To create a cluster:
 5. In the **Storage** section, select **Volume Type**, and in **Volume Properties** the type and amount of storage needed for your cluster.
    !!! Note
        EDB Cloud currently supports Azure Premium SSD storage types. See [the Azure documentation](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd) for more information.
-6. In the **Networking** section, Whether to use private or public networking using the **Networking** slide button. Networking is set to Public by default. Public means that any client can connect to your cluster’s public IP address over the internet.
-Private networking allows only IP addresses within your private network to connect to your cluster.
+6. In the **Networking** section, you specify whether to use private or public networking. Networking is set to Public by default. Public means that any client can connect to your cluster’s public IP address over the internet. 
+Private networking allows only IP addresses within your private network to connect to your cluster. See [Cluster networking architecture](01_cluster_networking) for more information.
 7. To optionally make updates to your database configuration parameters, select **Next: DB Configuration**.
 
 ## DB Configuration tab

product_docs/docs/edbcloud/beta/index.mdx → product_docs/docs/biganimal/release/index.mdx

@@ -1,6 +1,6 @@
 ---
-title: EDB Cloud
-description: "EDB Cloud: DBaaS for PostgresSQL "
+title: BigAnimal
+description: "BigAnimal: DBaaS for PostgresSQL "
 indexCards: simple
 hideVersion: true
 directoryDefaults:
@@ -12,5 +12,5 @@ navigation:
   - administering_cluster
   - pricing_and_billing
   - reference
-  - release_notes
+
 ---

product_docs/docs/edbcloud/beta/overview/02_high_availibility.mdx → product_docs/docs/biganimal/release/overview/02_high_availibility.mdx

@@ -2,7 +2,7 @@
 title: "Supported architectures"
 ---
 
-EDB Cloud enables deploying a cluster with or without high availability. The option is controlled with the **High Availablity** slide button on the [Create Cluster](https://portal.edbcloud.com/create-cluster) page in the [EDB Cloud](https://portal.edbcloud.com) portal.    
+BigAnimal enables deploying a cluster with or without high availability. The option is controlled with the **High Availablity** slide button on the [Create Cluster](https://portal.biganimal.com/create-cluster) page in the [BigAnimal](https://portal.biganimal.com) portal.    
 
 ## High availability - enabled
 
@@ -12,7 +12,7 @@ The high availability option is provided to minimize downtime in cases of failur
 * Replicas are usually called _standby servers_ and can also be used for read-only workloads.
 * In case of temporary or permanent unavailability of the primary, a standby replica will become the primary.
 
-![*EDB Cloud Cluster4*](images/high-availability.png)
+![*BigAnimal Cluster4*](images/high-availability.png)
 
 Incoming client connections are always routed to the current primary. In case of failure of the primary, a standby replica will automatically be promoted to primary and new connections will be routed to the new primary. When the old primary recovers, it will re-join the cluster as a replica.
 
@@ -24,4 +24,4 @@ For non-production use cases where high availability is not a primary concern, a
 
 In case of permanent unavailability of the primary, a restore from a backup is required. 
 
-![*EDB Cloud Cluster4*](images/ha-not-enabled.png )
+![*BigAnimal Cluster4*](images/ha-not-enabled.png )

product_docs/docs/edbcloud/beta/overview/03_security.mdx → product_docs/docs/biganimal/release/overview/03_security.mdx

@@ -2,11 +2,11 @@
 title: "Security"
 ---
 
-EDB Cloud runs in your own cloud account, isolates your data from other users, and gives you control over our access to it. The key security features are:
-- **Data isolation:** Clusters are installed and managed in your cloud environment. Complete segregation of your data is ensured: your data never leaves your cloud account, and compromise of another EDB Cloud customer's systems does not put your data at risk.
+BigAnimal runs in your own cloud account, isolates your data from other users, and gives you control over our access to it. The key security features are:
+- **Data isolation:** Clusters are installed and managed in your cloud environment. Complete segregation of your data is ensured: your data never leaves your cloud account, and compromise of another BigAnimal customer's systems does not put your data at risk.
 
 - **Granular access control:** You can use Single Sign On (SSO) and define your own sets of roles and Role Based Access Control (RBAC) policies to manage your individual cloud environments. See [Managing portal access](../administering_cluster/01_user_access) for more information. 
-- **Data encryption:** All data in EDB Cloud is encrypted in motion and at rest. Network traffic is encrypted using Transport Layer Security (TLS) v1.2 or greater, where applicable. Data at rest is encrypted using AES with 256 bit keys. Data encryption keys are envelope encrypted and the wrapped data encryption keys are securely stored in an Azure Key Vault instance in your account. Encryption keys never leave your environment.
+- **Data encryption:** All data in BigAnimal is encrypted in motion and at rest. Network traffic is encrypted using Transport Layer Security (TLS) v1.2 or greater, where applicable. Data at rest is encrypted using AES with 256 bit keys. Data encryption keys are envelope encrypted and the wrapped data encryption keys are securely stored in an Azure Key Vault instance in your account. Encryption keys never leave your environment.
 - **Portal audit logging:** Activities in the portal, such as those related to user roles, organization updates, and cluster creation and deletion are tracked automatically and viewed in the activity log.  
 - **Database logging and auditing:** Functionality to track and analyze database activities is enabled automatically. For PostgreSQL, the PostgreSQL Audit Extension (pgAudit) is enabled automatically for you when deploying a Postgres cluster. For EDB Postgres Advanced Server, the EDB Audit extension (edbAudit) is enabled automatically for you. 
     - **pgAudit:** The classes of statements being logged for pgAudit are set globally on a cluster with `pgaudit.log = 'write,ddl'`. The following statements made on tables will be logged by default when the cluster type is PostgreSQL: `INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, AND `COPY`. All `DDL` will be logged. 

product_docs/docs/edbcloud/beta/overview/04_responsibility_model.mdx → product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx

@@ -2,7 +2,7 @@
 title: "Responsibility model"
 ---
 
-Security and confidentiality is a shared responsibility between you and EDB. EDB provides a secure platform that enables you to create and maintain secure database clusters deployed on EDB Cloud. You have numerous responsibilities around the security of your clusters and data held within them.
+Security and confidentiality is a shared responsibility between you and EDB. EDB provides a secure platform that enables you to create and maintain secure database clusters deployed on BigAnimal. You have numerous responsibilities around the security of your clusters and data held within them.
 
 The following responsibility model describes the distribution of specific responsibilities between you and EDB.
 
@@ -30,4 +30,4 @@ The following responsibility model describes the distribution of specific respon
 
 ## Credential management 
 - EDB is responsible for making credentials available to customers.
-- You are responsible for managing and securing your passwords, both for EDB Cloud and your database passwords.
+- You are responsible for managing and securing your passwords, both for BigAnimal and your database passwords.

product_docs/docs/edbcloud/beta/overview/05_database_version_policy.mdx → product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx

@@ -19,7 +19,7 @@ PostgreSQL and EDB Postgres Advanced Server major versions are supported from th
 
 ## Minor version support
 
-EDB performs periodic maintenance to ensure stability and security. EDB automatically performs minor version upgrades and patch updates as part of periodic maintenance. Customers are notified within the EDB Cloud portal prior to maintenance occurring. Minor versions are not user configurable. 
+EDB performs periodic maintenance to ensure stability and security. EDB automatically performs minor version upgrades and patch updates as part of periodic maintenance. Customers are notified within the BigAnimal portal prior to maintenance occurring. Minor versions are not user configurable. 
 
 EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance.
 

product_docs/docs/edbcloud/beta/overview/06_support.mdx → product_docs/docs/biganimal/release/overview/06_support.mdx

@@ -2,18 +2,18 @@
 title: "Support options"
 ---
 
-If you experience problems with EDB Cloud, you have several options to engage with EDB's Support team to get help. If you have an EDB Cloud account, you can go directly to the Support portal or the EDB Cloud portal to open a support case, or you can leave Support a message using the Support Case widget. 
+If you experience problems with BigAnimal, you have several options to engage with EDB's Support team to get help. If you have an BigAnimal account, you can go directly to the Support portal or the BigAnimal portal to open a support case, or you can leave Support a message using the Support Case widget. 
 
 If you can’t log in to your account, send us an email to [[email protected]](mailto:[email protected]).
 
 ## Creating a support case from the Support portal (recommended)
 
 1. Initiate a support case using any one of these options:
 
-    - Go to the [Support portal](https://support.edbcloud.com/hc/en-us) and select **Submit a request** at the top right of the page.
+    - Go to the [Support portal](https://support.biganimal.com/hc/en-us) and select **Submit a request** at the top right of the page.
 
-    - Log in to [EDB Cloud](https://portal.edbcloud.com), select the question mark (?) at the top right of the page, select **Support Portal**, and select **Submit a request** at the top right of the page.
-    - Log in to [EDB Cloud](https://portal.edbcloud.com), select the question mark (?) at the top right of the page, select **Create Support ticket**.
+    - Log in to [BigAnimal](https://portal.biganimal.com), select the question mark (?) at the top right of the page, select **Support Portal**, and select **Submit a request** at the top right of the page.
+    - Log in to [BigAnimal](https://portal.biganimal.com), select the question mark (?) at the top right of the page, select **Create Support ticket**.
 1. Enter a description in the **Subject** field.
 
 1. (Optional) Select the cluster name from the **Cluster name** list.
@@ -23,7 +23,7 @@ If you can’t log in to your account, send us an email to [cloudsupport@enterpr
 
 ## Creating a support case from the **Support** widget
 
-1. Log in to EDB Cloud and select **Support** on the bottom of the left navigation pane. 
+1. Log in to BigAnimal and select **Support** on the bottom of the left navigation pane. 
 
 1. Fill in the **Leave us a message** form.
     1. (Optional) The **Your Name** field is pre-filled, but you can edit it.

product_docs/docs/edbcloud/beta/overview/index.mdx → product_docs/docs/biganimal/release/overview/index.mdx

@@ -3,7 +3,7 @@ title: "Overview of service"
 ---
 <div id="requirements_overview" class="registered_link"></div>
 
-EDB Cloud is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account, and operated by the Postgres experts. EDB Cloud makes it easy to set up, manage, and scale your databases. Provision [PostgreSQL](https://www.enterprisedb.com/docs/supported-open-source/postgresql/) or [EDB Postgres Advanced Server](https://www.enterprisedb.com/docs/epas/latest/) with Oracle compatibility. 
+BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account, and operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. Provision [PostgreSQL](https://www.enterprisedb.com/docs/supported-open-source/postgresql/) or [EDB Postgres Advanced Server](https://www.enterprisedb.com/docs/epas/latest/) with Oracle compatibility. 
 
 
 

product_docs/docs/edbcloud/beta/pricing_and_billing/index.mdx → product_docs/docs/biganimal/release/pricing_and_billing/index.mdx

@@ -2,7 +2,7 @@
 title: "Pricing and billing "
 ---
 
-This section covers the pricing breakdown for EDB Cloud as well as how to view invoices and infrastructure usage through Microsoft Azure.
+This section covers the pricing breakdown for BigAnimal as well as how to view invoices and infrastructure usage through Microsoft Azure.
 
 ## Pricing
 Pricing is based on the number of Virtual Central Processing Units (vCPUs) provisioned for the database software offering. Consumption of vCPUs is metered hourly. A deployment is comprised of either one instance or one primary and two replica instances of either PostgreSQL or EDB Postgres Advanced Server. When high availability is enabled, the number of vCPU per instance should be multiplied by three to calculate the full price for all resources used. See the full cost breakdown below:
@@ -18,4 +18,4 @@ Pricing is based on the number of Virtual Central Processing Units (vCPUs) provi
 All billing is handled directly by Microsoft Azure. Invoices and usage can be viewed on the Azure Portal billing page. [Learn more](https://docs.microsoft.com/en-us/azure/cost-management-billing/)
 
 ## Cloud infrastructure costs
-EDB does not bill you for cloud infrastructure such as compute, storage, data transfer, monitoring, and logging. EDB Cloud clusters run in your Microsoft Azure account. Azure bills you directly for the cloud infrastructure provisioned according to the terms of your account agreement. Invoices and usage can be viewed on the Azure Portal billing page. [Learn more](https://docs.microsoft.com/en-us/azure/cost-management-billing/)
+EDB does not bill you for cloud infrastructure such as compute, storage, data transfer, monitoring, and logging. BigAnimal clusters run in your Microsoft Azure account. Azure bills you directly for the cloud infrastructure provisioned according to the terms of your account agreement. Invoices and usage can be viewed on the Azure Portal billing page. [Learn more](https://docs.microsoft.com/en-us/azure/cost-management-billing/)