Merge pull request #3412 from EnterpriseDB/release/2022-12-05

Release: 2022-12-05

advocacy_docs/pg_extensions/advanced_storage_pack/using.mdx

@@ -21,7 +21,7 @@ CREATE TABLE nyse_symbol (
 
 A scenario where Autocluster would be useful is with an Internet of Things (IoT) data, which are usually inserted with many rows that relate to each other and often use append-only data. When using heap instead of Autocluster, Postgres can't cluster together these related rows, so access to the set of rows touches many data blocks, can be very slow, and input/output heavy.
 
-The following example is for an IoT of thermostats which report a houses's temperature and temperature settings every 60 seconds:
+The following example is for an IoT of thermostats which report house temperatures and temperature settings every 60 seconds:
 
 ```sql
 CREATE TABLE iot (
@@ -63,14 +63,14 @@ When you select the data from the IoT table, you can see from the ctid location
 ```sql
 SELECT ctid, thermostat_id, recordtime FROM iot;
 __OUTPUT__
- ctid  | thermostat_id | recordtime
--------+-------+---------
- (0,1) |     456 | 12:01
- (2,2) |     8945| 04:55
- (0,2) |     456  | 15:32
- (3,2) |     6785| 01:36
- (0,3) |     456 | 19:25
- (2,5) |     5678| 03:44
+ctid   | thermostat_id | recordtime
+-------+---------------+------------
+ (0,1) |           456 |      12:01
+ (2,2) |          8945 |      04:55
+ (0,2) |           456 |      15:32
+ (3,2) |          6785 |      01:36
+ (0,3) |           456 |      19:25
+ (2,5) |          5678 |      03:44
 (6 rows)
 ```
 
@@ -184,7 +184,7 @@ Select the ctid from the data for a given stock symbol to see in the output how
 ```sql
 SELECT ctid, * FROM nyse_trade WHERE nyse_symbol_id = 1000 ORDER BY trade_time DESC LIMIT 10;
 __OUTPUT__
-   ctid    | nyse_symbol_id |        trade_time        | trade_price | trade_volume 
+ctid       | nyse_symbol_id |        trade_time        | trade_price | trade_volume 
 -----------+----------------+--------------------------+-------------+--------------
  (729,71)  |           1000 | Fri Nov 18 11:13:51 2022 |   11.265938 |        72662
  (729,22)  |           1000 | Fri Nov 18 11:08:39 2022 |   11.262747 |        50897

product_docs/docs/biganimal/release/free_trial/detail/connect_to_a_cluster/connect_using_pgadmin.mdx

@@ -10,7 +10,7 @@ indexCards: none
 
 [The pgAdmin project](https://www.pgadmin.org/download/) allows you to inspect, monitor, manage, and query your cluster's databases from a desktop or web UI. 
 
-From the welcome page, select **Add New Server**. You'll be prompted to configure the connection.
+From the welcome page of pgAdmin, select **Add New Server**. You'll be prompted to configure the connection.
 
 Enter `BigAnimal Trial` for the name (or use the name you gave to your cluster!), and then select **Connection**.
 
@@ -19,7 +19,7 @@ Enter `BigAnimal Trial` for the name (or use the name you gave to your cluster!)
 3. Enter `edb_admin` in the **Username** field.
 4. Enter the password you provided when configuring your cluster in the **Password** field (you might want to save this for convenience while testing).
 
-Select **SSL** and change SSL mode to **Require**.
+Select **SSL** tab and change SSL mode to **Require**.
 
 Finally, select the **Save** button. pgAdmin tries to establish a connection to your database. When successful, it displays the dashboard 
 along with the list of available databases on the left.

product_docs/docs/biganimal/release/free_trial/detail/create_a_cluster/create_cluster_portal.mdx

@@ -20,30 +20,33 @@ You should now find yourself at the [Create Cluster page](https://portal.biganim
 
 In the free trial, the range of cluster options is somewhat limited but should be more than sufficient for demonstrating the capabilities of BigAnimal. 
 
+1. First you select your **Cluster Type**. Pick **Single Node**. If you're interested in learning more about the BigAnimal's high availability deployment options, see [Cluster types](/biganimal/release/overview/02_high_availability).
+1. **Provider** is either AWS or Azure; BigAnimal works the same on either one, so choose the one you're familiar with.
 1. Use **Cluster Name** to describe the purpose of the cluster. For example, "Test for Advanced Server on AWS."
-2. **Password** is the admin password for the cluster, so pick a strong one! Note that this is independent of your EDB account.
-3. **Database Type** is one of:
+1. **Password** is the admin password for the cluster, so pick a strong one! Note that this is independent of your EDB account.
+1. **Database Type** is one of:
 
    - **EnterpriseDB PostgreSQL Advanced Server** for Oracle database compatibility
    - **PostgreSQL** for official community builds of standard PostgreSQL
 
     So if you're interested in EDB's enhancements to PostgreSQL for Oracle database compatibility, choose Advanced Server; otherwise, choose PostgreSQL.
-4. **Postgres Version** allows you to select from among the supported versions for either database type.
-4. **Provider** is either AWS or Azure; BigAnimal works the same on either one, so choose the one you're familiar with.
-5. **Region** options depend on the provider you chose; pick the one closest to you.
-6. **Network Connectivity** is restricted to a public IP for the trial, but you can restrict access to trusted networks by
+1. **Postgres Version** allows you to select from among the supported versions for either database type.
+
+1. **Region** options depend on the provider you chose; pick the one closest to your application.
+
+1. For **Instance Type** and **Storage**, only one option is available for each field during the trial, so just choose that. The full set of instance types and storage options are available in the BigAnimal paid subscriptions.
+1. **Network Connectivity** is restricted to a public IP for the trial, but you can restrict access to trusted networks by
    selecting the **Use allowlists to restrict network access** check box and specifying one or more [CIDR blocks](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) 
    to allow access from.
 
-For **Instance Type** and **Storage**, only one option is available for each field during the trial, so just choose that.
 
 ### The DB Configuration tab
 
 This is entirely optional, but if you're curious, you can find a full set of PostgreSQL configuration options on this tab, allowing you to tune a cluster for specific needs or resource constraints.
 
-### The Availability tab
+### The Additional Settings tab
 
-This page configures high availability, but that feature isn't available in the trial. Skip this tab unless you're curious.
+This page has backup retention period, ready-only workload, and IAM authentication settings, but those features aren't available in the trial. Skip this tab unless you're curious.
 
 ## Provisioning 
 

product_docs/docs/biganimal/release/getting_started/activating_regions.mdx

@@ -13,23 +13,23 @@ Each region you activate displays a status. The status is available on the Creat
 
 ## Activate a new region from the Regions page
 
-You can activate a region ahead of time using the **Admin > Regions** page. Alternatively, you can activate a region by selecting an inactive region at the time of cluster creation or restore.
+You can activate a region ahead of time using the **Regions** page. Alternatively, you can activate a region by selecting an inactive region at the time of cluster creation or restore.
 
-1. To activate a region ahead of cluster creation, go to the **Admin > Regions** page.
+1. To activate a region ahead of cluster creation, go to the **Regions** page.
 
 1. If you haven't set up your cloud server provider (CSP), you are prompted to do so. See [Connecting your cloud](/biganimal/latest/getting_started/02_connecting_to_your_cloud/).
 
 1. When your cloud server provider is set up, you see a list of regions associated with it on the Regions page.
 
-1. Select the region you want to activate. You can activate multiple regions where you plan on adding clusters. 
+1. Select **Activate New Region**, select your cloud provider, and the region you want to activate. You can activate multiple regions where you plan on adding clusters. 
 
 1. Select **Activate Region(s)**.
 
 ## Suspend, reactivate, or delete a region
 
 Before you suspend or delete a region you must delete all clusters in that region.
 
-1. On the left panel, under Admin, select **Regions**.
+1. On the left panel, select **Regions**.
 
 1. A list of previously activated regions appears.