Merge pull request #4689 from EnterpriseDB/release/2023-08-24a

Release: 2023-08-24a
EnterpriseDB · Aug 24, 2023 · da3cc9d · da3cc9d · github-actions · Aug 24, 2023
2 parents a9b4c3f + 2b268a9
commit da3cc9d
Show file tree

Hide file tree

Showing 42 changed files with 99 additions and 94 deletions.
diff --git a/...cy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx b/...cy_docs/partner_docs/CohesityDataProtectforPostgreSQL/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Cohesity DataProtect for PostgreSQL'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |

diff --git a/...sityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx b/...sityDataProtectforPostgreSQL/04-ConfiguringCohesityDataProtectforPostgreSQL.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Cohesity DataProtect for PostgreSQL'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing Cohesity DataProtect for PostgreSQL with EDB Postgres Advanced Server requires the following components:

diff --git a/...s/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx b/...s/CohesityDataProtectforPostgreSQL/05-UsingCohesityDataProtectforPostgreSQL.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Cohesity DataProtect for PostgreSQL usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 These use cases show how backups are taken and restored from EDB Postgres Advanced Server using Cohesity DataProtect for PostgreSQL.
 

diff --git a/...s/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx b/...s/partner_docs/CohesityDataProtectforPostgreSQL/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used in the certification of Cohesity DataProtect for PostgreSQL'
+description: 'Overview of the certification environment'
 ---
 
 |  &nbsp;    | &nbsp; |

diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/02-PartnerInformation.mdx
@@ -1,11 +1,11 @@
 ---
 title: 'Partner information'
-description: 'Details of the Partner'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |
 | ----------- | ----------- |
-| **Partner Name**      | Commvault       |
+| **Partner name**      | Commvault       |
 | **Partner product**   |  Commvault Backup & Recovery       |
 | **Website**      |    https://www.commvault.com/   |
 | **Version**   |  Commvault Backup & Recovery 11.32      |

diff --git a/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/CommvaultBackupandRecovery/07-SupportandLogging.mdx
@@ -1,23 +1,25 @@
 ---
-title: 'Support and Logging Details'
+title: 'Support and logging details'
 description: 'Details of the support process and logging information'
 ---
 
 ## Support
 
-Technical support for the use of these products is provided by both EDB and Commvault.  A proper support contract is required to be in place at both EDB and Commvault.  A support ticket can be opened on either side to start the process.  If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels.  This will allow both companies to work together to help the customer as needed.
+Technical support for the use of these products is provided by both EDB and Commvault. A support contract must be in place at both EDB and Commvault. You can open a support ticket with either company to start the process. If it's determined through the support ticket that resources from the other vendor are required, open a support ticket with that vendor through normal support channels. This approach allows both companies to work together to help you as needed.
 
 ## Logging
 
-**EDB Postgres Advanced Server Logs:**
+The following logs are available.
 
-Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs.
+### EDB Postgres Advanced Server logs
 
-**EDB Postgres Extended Server Logs**
+Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance. From there, you can navigate to `log` or `current_logfiles`. Or, you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs.
 
-Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options.  An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`.
+### EDB Postgres Extended Server logs
 
-**PostgreSQL Server Logs**
+Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance. From there you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options.  An example of the full path to view EDB Postgres Extended logs is `/var/lib/edb-pge/15/data/log`.
+
+### PostgreSQL Server logs
 
 The default log directories for PostgreSQL logs vary depending on the operating system:
 
@@ -27,16 +29,18 @@ The default log directories for PostgreSQL logs vary depending on the operating
 
 - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log`
 
-** Commvault Logs**
+### Commvault logs
+
+You can find Commvault logs using either of these methods:
 
-Commvault logs can be found a few ways.  A first way is within the Content Store directory/folder in the Commvault folder on your system.  For example if on a Windows system the Log File path would be `C:\Program Files\Commvault\ContentStore\LogFiles` where you can then see all of the differnt types of logs Commvault collects.  
+- Look in the Content Store directory/folder in the Commvault folder on your system. For example, on a Windows system, the log file path is `C:\Program Files\Commvault\ContentStore\LogFiles`. There you can see all of the different types of logs Commvault collects.  
 
-You can also gather some job specific logs within the Commvault interface.
+- Gather some job-specific logs in the Commvault interface:
 
-1. Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to `Jobs > Job History`.
+  1. Open Commvault Backup & Recovery's Command Center. From the navigation pane, go to **Jobs > Job History**.
 
-2. Find the specific job you would like to view logs for and click on the `...` beside that job.
+  2. Find the specific job you want to view logs for, and select `...` next to that job.
 
-3. Select `View Logs`.  
+  3. Select **View Logs**.  
 
-  ![View Job Logs](Images/CommvaultViewLogsForJob.png)
+    ![View Job Logs](Images/CommvaultViewLogsForJob.png)
diff --git a/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx b/advocacy_docs/partner_docs/DBeaverPRO/07-SupportandLogging.mdx
@@ -1,23 +1,25 @@
 ---
-title: 'Support and Logging Details'
+title: 'Support and logging details'
 description: 'Details of the support process and logging information'
 ---
 
 ## Support
 
-Technical support for the use of these products is provided by both EDB and DBeaver.  A proper support contract is required to be in place at both EDB and DBeaver.  A support ticket can be opened on either side to start the process.  If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels.  This will allow both companies to work together to help the customer as needed.
+Technical support for the use of these products is provided by both EDB and DBeaver. A support contract must be in place at both EDB and DBeaver. You can open a support ticket with either company to start the process. If it's determined through the support ticket that resources from the other vendor are required, open a support ticket with that vendor through normal support channels. This approach allows both companies to work together to help you as needed.
 
 ## Logging
 
-**EDB Postgres Advanced Server Logs:**
+The following logs are available.
 
-Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs.
+### EDB Postgres Advanced Server logs
 
-**EDB Postgres Extended Server Logs**
+Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance. From there, you can navigate to `log` or `current_logfiles`. Or, you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs.
 
-Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance and from here you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options.  An example of the full path to view EDB Postgres Extended logs: `/var/lib/edb-pge/15/data/log`.
+### EDB Postgres Extended Server logs
 
-**PostgreSQL Server Logs**
+Navigate to the `Data` directory in your chosen EDB Postgres Extended Server instance. From there you can navigate to `log`, or you can navigate to the `postgresql.conf` file where you can customize logging options.  An example of the full path to view EDB Postgres Extended logs is `/var/lib/edb-pge/15/data/log`.
+
+### PostgreSQL Server logs
 
 The default log directories for PostgreSQL logs vary depending on the operating system:
 
@@ -27,15 +29,13 @@ The default log directories for PostgreSQL logs vary depending on the operating
 
 - Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log`
 
-** DBeaver Logs**
-
-If you are experiencing errors during the DBeaver runtime you can gather those within the DBeaver Pro interface.  
+## DBeaver logs
 
-1. On the top menu bar navigate to `Window` and select it.
+If you experience errors during the DBeaver runtime, you can gather them in the DBeaver Pro interface:  
 
-2. Scroll down to `Show View`.
+1. At the top menu bar, select **Window**.
 
-3. In the menu options that come up select `Error Log` and this will contain all the errors that occur during the DBeaver runtime.  
+2. Select **Show View > Error Log**. The log contains all the errors that occur during the DBeaver runtime.  
   ![DBeaver Log Viewer](Images/DBeaverLogViewer.png)
 
 4. You can save and attach these logs to a support ticket or bug report to DBeaver support.

diff --git a/...ocs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx b/...ocs/partner_docs/EsriArcGISProandEsriArcGISEnterprise/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Esri ArcGIS Pro and Esri ArcGIS Enterprise'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |

diff --git a/...oandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx b/...oandEsriArcGISEnterprise/04-ConfiguringEsriArcGISProandEsriArcGISEnterprise.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Esri ArcGIS Pro and Esri ArcGIS Enterprise'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing Esri ArcGIS Pro and Esri ArcGIS Enterprise with EDB Postgres Advanced Server requires the following components:

diff --git a/...cGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx b/...cGISProandEsriArcGISEnterprise/05-UsingEsriArcGISProandEsriArcGISEnterprise.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Esri ArcGIS Pro and Esri ArcGIS Enterprise usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 
 ## Create file geodatabase

diff --git a/...rtner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx b/...rtner_docs/EsriArcGISProandEsriArcGISEnterprise/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used in the certification of Esri ArcGIS Pro and Esri ArcGIS Enterprise'
+description: 'Overview of the certification environment'
 ---
 
 |  &nbsp;    | &nbsp; |

diff --git a/advocacy_docs/partner_docs/HashicorpVault/index.mdx b/advocacy_docs/partner_docs/HashicorpVault/index.mdx
@@ -6,7 +6,7 @@ directoryDefaults:
 ---
 
 
-[Partner Program Logo](Images/PartnerProgram.jpg.png)
+![Partner Program Logo](Images/PartnerProgram.jpg.png)
 
 <h1 style="text-align: center;">EDB GlobalConnect Technology Partner Implementation Guide</h1>
 <h3 style="text-align: center;">Hashicorp Vault</h3>

diff --git a/..._docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx b/..._docs/HashicorpVaultTransitSecretsEngine/04-ConfiguringTransitSecretsEngine.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough on configuring the integration'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing Hashicorp Vault with EDB Postgres Advanced Server version 15.2 and later or EDB Postgres Extended Server version 15.2 and later requires the following components:

diff --git a/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx b/advocacy_docs/partner_docs/ImpervaDataSecurityFabric/index.mdx
@@ -5,7 +5,7 @@ directoryDefaults:
     iconName: handshake
 ---
 
-[Partner Program Logo](Images/PartnerProgram.jpg.png)
+![Partner Program Logo](Images/PartnerProgram.jpg.png)
 <h1 style="text-align: center;">EDB GlobalConnect Technology Partner Implementation Guide</h1>
 <h3 style="text-align: center;">Imperva Data Security Fabric</h3>
 

diff --git a/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/LiquibasePro/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Liquibase Pro'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |

diff --git a/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx b/advocacy_docs/partner_docs/LiquibasePro/04-ConfiguringLiquibasePro.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Liquibase Pro'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing Liquibase with EDB Postgres Advanced Server requires the following components:

diff --git a/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx b/advocacy_docs/partner_docs/LiquibasePro/05-UsingLiquibasePro.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Liquibase Pro usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 
 Liquibase is a development tool that allows you to apply changes to the EDB database using the Liquibase CLI and view them on the Liquibase Hub.

diff --git a/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/LiquibasePro/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used in the certification of Liquibase Pro'
+description: 'Overview of the certification environment'
 ---
 
 |  &nbsp;    | &nbsp; |

diff --git a/...y_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx b/...y_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'ConfiguringC'
+title: 'Configuring'
 description: 'Walkthrough of configuring the integration'
 ---
 

diff --git a/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/QuestToadEdge/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Quest Toad Edge'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |

diff --git a/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx b/advocacy_docs/partner_docs/QuestToadEdge/04-ConfiguringQuestToadEdge.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Quest Toad Edge'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing Quest Toad Edge with EDB Postgres Advanced Server or EDB Postgres Extended Server requires the following components: 

diff --git a/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx b/advocacy_docs/partner_docs/QuestToadEdge/05-UsingQuestToadEdge.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Quest Toad Edge usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 
 After you connect an instance of EDB Postgres Advanced Server or EDB Postgres Extended to Quest Toad Edge, you can access the capabilities of Toad Edge. 

diff --git a/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/QuestToadEdge/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used in the certification of Quest Toad Edge'
+description: 'Overview of the certification environment'
 redirects: 
   - /partner_docs/ToadEdgeGuide/06-CertificationEnvironment/
 ---

diff --git a/..._docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx b/..._docs/partner_docs/RepostorDataProtectorforPostgreSQL/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Repostor Data Protector for PostgreSQL'
+description: 'Details of the partner'
 redirects:
   - /partner_docs/RepostorGuide/02-PartnerInformation/
 ---

diff --git a/...DataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx b/...DataProtectorforPostgreSQL/04-ConfiguringRepostorDataProtectorforPostgreSQL.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Repostor Data Protector for PostgreSQL'
+description: 'Walkthrough of configuring the integration'
 ---
 
 ## Prerequisites

diff --git a/...postorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx b/...postorDataProtectorforPostgreSQL/05-UsingRepostorDataProtectorforPostgreSQL.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Repostor Data Protector for PostgreSQL usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 The current RDP version is a command-line client. You run three commands:
 `postgresbackup`, `postgresquery`, and `postgresrestore`. The logwriter and logreader tools are called by PostgreSQL during execution of `archive_command` and `restore_command`.

diff --git a/...partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx b/...partner_docs/RepostorDataProtectorforPostgreSQL/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used for certifying Repostor Data Protector for PostgreSQL'
+description: 'Overview of the certification environment'
 redirects:
   - /partner_docs/RepostorGuide/06-CertificationEnvironment/
 ---

diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for SIB Visions VisionX'
+description: 'Details of the partner'
 
 ---
 | &nbsp;     | &nbsp; |

diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/04-ConfiguringSIBVisionsVisionX.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring SIB Visions VisionX'
+description: 'Walkthrough of configuring the integration'
 ---
 
 Implementing SIB Visions VisionX with EDB Postgres Advanced Server or EDB Postgres Extended Server requires the following components:

diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/05-UsingSIBVisionsVisionX.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple SIB Visions VisionX usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 
 These examples walk you though some of the common usage scenarios that can be used with EDB Postgres Advanced Server or EDB Postgres Extended Server. These are examples to help get you started and show how the products can work together.

diff --git a/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/SIBVisionsVisionX/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used for certifying SIB Visions VisionX'
+description: 'Overview of the certification environment'
 ---
 
 |  &nbsp;    | &nbsp; |

diff --git a/...s/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx b/...s/partner_docs/ThalesCipherTrustTransparentEncryption/02-PartnerInformation.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Partner information'
-description: 'Details for Thales CipherTrust Transparent Encryption (CTE)'
+description: 'Details of the partner'
 
 ---
 

diff --git a/...tTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx b/...tTransparentEncryption/04-ConfiguringThalesCipherTrustTransparentEncryption.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Configuring'
-description: 'Walkthrough of configuring Thales CipherTrust Transparent Encryption (CTE)'
+description: 'Walkthrough of configuring the integration'
 ---
 
 

diff --git a/...erTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx b/...erTrustTransparentEncryption/05-UsingThalesCipherTrustTransparentEncryption.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Using'
-description: 'Walkthroughs of multiple Thales CipherTrust Transparent Encryption (CTE) usage scenarios'
+description: 'Walkthrough of example usage scenarios'
 ---
 
 CTE protects data either at the file level or at the storage device level. A CTE agent running on the Postgres host manages the files behind a GuardPoint by enforcing the policy associated with it and communicates data access events to the CipherTrust Manager for logging. A GuardPoint is usually associated with a Linux mount point or a Windows volume but can also be associated with a directory subtree.

diff --git a/...ner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx b/...ner_docs/ThalesCipherTrustTransparentEncryption/06-CertificationEnvironment.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Certification environment'
-description: 'Overview of the certification environment used in the certification of Thales CipherTrust Transparent Encryption (CTE)'
+description: 'Overview of the certification environment'
 ---
 
 |  &nbsp;    | &nbsp; |

diff --git a/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/VeritasNetBackupforPostgreSQL/02-PartnerInformation.mdx
@@ -1,13 +1,13 @@
 ---
 title: 'Partner information'
-description: 'Details for Veritas NetBackup for PostgreSQL'
+description: 'Details of the partner'
 redirects:
   - /partner_docs/VeritasGuide/02-PartnerInformation/
 ---
 | &nbsp;     | &nbsp; |
 | ----------- | ----------- |
 | **Partner name**      |  Veritas     |
-| **Partner Product**   |   NetBackup for PostgreSQL    |
+| **Partner product**   |   NetBackup for PostgreSQL    |
 | **Website**      |   https://www.veritas.com/   |
 | **Version & platform**   |   NetBackup for PostgreSQL 9.1: Linux, Windows     |
 | **Product description**      |  Veritas NetBackup gives enterprise IT a simple and powerful way to ensure the integrity and availability of their dataa&mdash;from edge to core to cloud. Veritas NetBackup for PostgreSQL Agent extends the capabilities of NetBackup to include backup and restore of PostgreSQL databases.     |