diff --git a/install_template/deploy.mjs b/install_template/deploy.mjs
index 784cba25d3d..ad262ebffa4 100644
--- a/install_template/deploy.mjs
+++ b/install_template/deploy.mjs
@@ -243,8 +243,6 @@ const moveDoc = async (product, platform, version) => {
       (ctx) => `epas/12/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_deb11_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB Postgres Advanced Server", version: 12}, platform: {name: "Ubuntu 18.04"}}, 
       (ctx) => `epas/12/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "EDB Postgres Advanced Server", version: 12}, platform: {name: "Ubuntu 20.04"}}, 
-      (ctx) => `epas/12/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu20_${fmtArchFilename(ctx)}.mdx`),
 
     when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "CentOS 7"}}, 
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_centos7_${fmtArchFilename(ctx)}.mdx`),
@@ -262,14 +260,10 @@ const moveDoc = async (product, platform, version) => {
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_sles12_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "SLES 15"}}, 
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_sles15_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Debian 10"}}, 
-      (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_deb10_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Debian 11"}}, 
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_deb11_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Ubuntu 18.04"}}, 
       (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu18_${fmtArchFilename(ctx)}.mdx`),
-    when({product: {name: "EDB Postgres Advanced Server", version: 11}, platform: {name: "Ubuntu 20.04"}}, 
-      (ctx) => `epas/11/epas_inst_linux/installing_epas_using_edb_repository/${fmtArchPath(ctx)}/epas_ubuntu20_${fmtArchFilename(ctx)}.mdx`),
 
 
     when({product: {name: "Failover Manager", version: 4}, platform: {name: "CentOS 7"}}, 
diff --git a/install_template/templates/products/edb-odbc-connector/base.njk b/install_template/templates/products/edb-odbc-connector/base.njk
index cefe59ea112..7f8b0f1c712 100644
--- a/install_template/templates/products/edb-odbc-connector/base.njk
+++ b/install_template/templates/products/edb-odbc-connector/base.njk
@@ -3,3 +3,10 @@
 {% block prodprereq %}{% include "platformBase/_epasinstalldiffserver.njk" %}
 
 {% endblock prodprereq %}
+{% block installCommand %}{% block odbcconnector %}
+```shell
+sudo {{packageManager}} -y install {{ packageName }}
+sudo {{packageManager}} -y install {{ packageName }}-devel
+```
+{% endblock odbcconnector %}{% endblock installCommand %}
+
diff --git a/install_template/templates/products/edb-odbc-connector/debian.njk b/install_template/templates/products/edb-odbc-connector/debian.njk
index a1fe7f20325..181434043b1 100644
--- a/install_template/templates/products/edb-odbc-connector/debian.njk
+++ b/install_template/templates/products/edb-odbc-connector/debian.njk
@@ -1,7 +1,7 @@
 {% extends "products/edb-odbc-connector/base.njk" %}
 {% block odbcconnector %}
 ```shell
-sudo apt-get install {{ packageName }}
-sudo apt-get install {{ packageName }}-dev
+sudo {{packageManager}} -y install {{ packageName }}
+sudo {{packageManager}} -y install {{ packageName }}-dev
 ```
 {% endblock odbcconnector %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/sles-12.njk b/install_template/templates/products/edb-odbc-connector/sles-12.njk
index 3b5f6694028..3df2c8c07ac 100644
--- a/install_template/templates/products/edb-odbc-connector/sles-12.njk
+++ b/install_template/templates/products/edb-odbc-connector/sles-12.njk
@@ -1,2 +1,8 @@
 {% extends "products/edb-odbc-connector/base.njk" %}
-{% set platformBaseTemplate = "sles-12" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-12" %}
+{% block odbcconnector %}
+```shell
+sudo {{packageManager}} -n install {{ packageName }}
+sudo {{packageManager}} -n install {{ packageName }}-devel
+```
+{% endblock odbcconnector %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/sles-15.njk b/install_template/templates/products/edb-odbc-connector/sles-15.njk
index e392f81aea9..59ffe22b880 100644
--- a/install_template/templates/products/edb-odbc-connector/sles-15.njk
+++ b/install_template/templates/products/edb-odbc-connector/sles-15.njk
@@ -1,2 +1,8 @@
 {% extends "products/edb-odbc-connector/base.njk" %}
-{% set platformBaseTemplate = "sles-15" %}
\ No newline at end of file
+{% set platformBaseTemplate = "sles-15" %}
+{% block odbcconnector %}
+```shell
+sudo {{packageManager}} -n install {{ packageName }}
+sudo {{packageManager}} -n install {{ packageName }}-devel
+```
+{% endblock odbcconnector %}
\ No newline at end of file
diff --git a/install_template/templates/products/edb-odbc-connector/ubuntu.njk b/install_template/templates/products/edb-odbc-connector/ubuntu.njk
index a1fe7f20325..181434043b1 100644
--- a/install_template/templates/products/edb-odbc-connector/ubuntu.njk
+++ b/install_template/templates/products/edb-odbc-connector/ubuntu.njk
@@ -1,7 +1,7 @@
 {% extends "products/edb-odbc-connector/base.njk" %}
 {% block odbcconnector %}
 ```shell
-sudo apt-get install {{ packageName }}
-sudo apt-get install {{ packageName }}-dev
+sudo {{packageManager}} -y install {{ packageName }}
+sudo {{packageManager}} -y install {{ packageName }}-dev
 ```
 {% endblock odbcconnector %}
\ No newline at end of file
diff --git a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx
index 51d6c3b30fd..2a900a8b6e6 100644
--- a/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx
+++ b/product_docs/docs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx
@@ -5,15 +5,15 @@ redirects:
 ---
 
 BigAnimal collects a wide set of metrics about Postgres instances and makes them available
-in your cloud platform. Most of these metrics are acquired directly from Postgres system tables,
-views, and functions. The Postgres documentation serves as the main reference for these metrics.
+in your cloud provider. Most of these metrics are acquired directly from Postgres system tables,
+views, and functions. The Postgres documentation is the main reference for these metrics.
 
-Some data from Postgres monitoring system views, tables, and functions are
+Some data from Postgres monitoring system views, tables, and functions is
 transformed to be easier to consume in Prometheus metrics format. For example,
 timestamp fields are generally converted to Unix epoch time and can be accompanied
 by a relative time-interval metric. Other metrics are aggregated into
 categories by label dimensions to limit the number of very specific and
-narrowly scoped individual metrics emitted. It is not very useful to
+narrowly scoped individual metrics emitted. It isn't useful to
 report the inactivity period of every single backend, for example, so backend
 statistics are aggregated by database, user, `application_name`, and backend
 state.
@@ -22,13 +22,13 @@ The number of tables in your database will impact the number of metrics in your
 impacting your cloud provider costs for storing these metrics. To ensure stability of the metrics pipeline, metrics may be dropped when the number of tables in your database exceeds 2500.
 
 Prometheus [labels](https://prometheus.io/docs/practices/naming/#labels)
-are included in the $.Message.labels JSON object.
+are included in the `$.Message.labels` JSON object.
 Dimensions vary depending on the individual metric and are documented
 separately for each group of related metrics.
 
 The available set of metrics is subject to change. Metrics might be added,
-removed or renamed. Where feasible, an effort will be made not to change the
-meaning or type of existing metrics without also changing the metric name.
+removed or renamed. Where possible, we change the metric name when changing the
+meaning or type of existing metrics.
 
 
 [comment1]: # "Generated content using script https://github.com/EnterpriseDB/starlight-scripts/blob/main/docs/metrics_to_markdown_txt.py"
@@ -37,32 +37,31 @@ meaning or type of existing metrics without also changing the metric name.
 
 Backend counts from `pg_stat_activity` aggregated by the listed label
 dimensions. Useful for identifying busy applications, excessive idle
-backends, etc.
+backends, and so on.
 
 Derived from the `pg_stat_activity` view.
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
-| `cnp_backends_state` | GAUGE | State of the backend (pg\_stat\_activity.state) mapped to integer enum. active = 1, idle = 2, idle in transaction = 3, idle in transaction (aborted) = 4, fastpath function call = 5, disabled = 6, and -1 = other/unrecognised |
 | `cnp_backends_n_backends` | GAUGE | Number of backends in this group |
 | `cnp_backends_max_tx_duration_seconds` | GAUGE | Maximum duration of a transaction in seconds in this group |
 | `cnp_backends_max_backend_xmin_age` | GAUGE | Maximum duration of a transaction in seconds in this group |
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
 | `datname` | Name of the database for this group of backends |
 | `usename` | Name of the user in this group of backends |
 | `application_name` | Name of the application for this group of backends |
+| `state` | State of the group of backends (pg\_stat\_activity.state) |
 
 ## `cnp_backends_waiting`
 
-Postgres-instance-level aggregate information on backends that are blocked
-waiting for locks. Does not count I/O waits or other reasons backends might
+Postgres instance-level aggregate information on backends that are blocked
+waiting for locks. Doesn't count I/O waits or other reasons backends might
 wait or be blocked.
 
 Derived from the `pg_locks` view.
@@ -73,12 +72,12 @@ Derived from the `pg_locks` view.
 
 ## `cnp_pg_database`
 
-Per-database metrics for each database in the postgres instance.
+Per-database metrics for each database in the Postgres instance.
 Includes per-database vacuum progress information.
 
 Derived from the `pg_database` catalog.
 
-See also `cnp_pg_stat_database`.
+See also [cnp_pg_stat_database](#cnp_pg_stat_database).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -88,8 +87,7 @@ See also `cnp_pg_stat_database`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -97,7 +95,7 @@ as dimensions in Azure Monitor:
 
 ## `cnp_pg_postmaster`
 
-Data on the postgres instance's managing "postmaster" process.
+Data on the Postgres instance's managing "postmaster" process.
 
 Derived from the `pg_postmaster_start_time()` function.
 
@@ -114,7 +112,7 @@ Derived from the `pg_last_xact_replay_timestamp()` function.
 
 Relevant only on standby replicas.
 
-See also `cnp_pg_stat_replication`, `cnp_pg_replication_slots`.
+See also [cnp_pg_stat_replication](#cnp_pg_stat_replication), [cnp_pg_replication_slots](#cnp_pg_replication_slots).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -123,17 +121,17 @@ See also `cnp_pg_stat_replication`, `cnp_pg_replication_slots`.
 
 ## `cnp_pg_replication_slots`
 
-Details about replication slots on a postgres instance. In most
+Details about replication slots on a Postgres instance. In most
 configurations, only the primary server has active replication clients,
 but other nodes can still have replication slots.
 
 Logical replication slots are specific to a database, whereas
 physical replication slots have an empty "database" label as they
-apply to the postgres instance as a whole.
+apply to the Postgres instance as a whole.
 
 Derived from the `pg_replication_slots` view.
 
-See also `cnp_pg_stat_replication`, `cnp_pg_replication`.
+See also [cnp_pg_stat_replication](#cnp_pg_stat_replication), [cnp_pg_replication](#cnp_pg_replication).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -142,8 +140,7 @@ See also `cnp_pg_stat_replication`, `cnp_pg_replication`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -157,13 +154,13 @@ server generally performs WAL archiving.
 
 WAL archiving is important for backup and restore. If WAL archiving is
 delayed or failing for too long, the point-in-time recovery backups for
-a postgres cluster will not be up to date. This condition has disaster recovery
+a Postgres cluster won't be up to date. This condition has disaster recovery
 implications and can potentially also affect failover.
 
-Occasional WAL archiving failures are normal, but a growing delay in the time
-since the last successful WAL archiving operation should be taken seriously.
+Occasional WAL archiving failures are normal, but pay attention to a growing delay in the time
+since the last successful WAL archiving operation.
 
-Metrics in this section are reset when a postgres stats reset is issued
+The following metrics are reset when a Postgres stats reset is issued
 on the db server.
 
 Derived from the `pg_stat_archiver` view.
@@ -182,18 +179,18 @@ Derived from the `pg_stat_archiver` view.
 
 ## `cnp_pg_stat_bgwriter`
 
-Stats for the postgres background writer and checkpointer processes, which
-are instance-wide and shared across all databases in a postgres instance.
+Stats for the Postgres background writer and checkpointer processes, which
+are instance-wide and shared across all databases in a Postgres instance.
 
 Very long delays between checkpoints on a busy system increase the time
 taken for it to return to read/write availability if crash recovery is
 required. Excessively frequent checkpoints can increase I/O load and the size
 of the WAL stream for backup and replication.
 
-The postgres documentation discusses checkpoints, dirty writeback, and
+The Postgres documentation discusses checkpoints, dirty writeback, and
 checkpoint tuning in detail.
 
-Metrics in this section are reset when a postgres stats reset is issued
+These metrics are reset when a Postgres stats reset is issued
 on the db server.
 
 Derived from the `pg_stat_bgwriter` catalog.
@@ -213,16 +210,16 @@ Derived from the `pg_stat_bgwriter` catalog.
 
 ## `cnp_pg_stat_database`
 
-This metrics group directly exposes the summary data postgres collects in its
+This metrics group directly exposes the summary data Postgres collects in its
 own `pg_stat_database` view. It contains statistical counters maintained by
-postgres for database activity.
+Postgres for database activity.
 
-Metrics in this section are reset when a postgres stats reset is issued
+These metrics are reset when a Postgres stats reset is issued
 on the db server.
 
 Derived from the `pg_stat_database` catalog.
 
-See also `cnp_pg_database`.
+See also [cnp_pg_database](#cnp_pg_database).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -244,8 +241,7 @@ See also `cnp_pg_database`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -255,16 +251,17 @@ as dimensions in Azure Monitor:
 
 These metrics provide information on conflicts between queries on a standby replica
 and the standby replica's replay of the change-stream from the primary. These are
-called recovery conflicts.
+called *recovery conflicts*.
 
 These metrics are unrelated to "INSERT ... ON CONFLICT" conflicts or
 multi-master replication row conflicts. They are relevant only on standby
 replicas.
 
-Metrics in this section are reset when a postgres stats reset is issued
+These metrics are reset when a Postgres stats reset is issued
 on the db server.
 
-Only defined on standby replicas.
+
+Defined only on standby replicas.
 
 Derived from the `pg_stat_database_conflicts` view.
 
@@ -278,8 +275,7 @@ Derived from the `pg_stat_database_conflicts` view.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -287,14 +283,14 @@ as dimensions in Azure Monitor:
 
 ## `cnp_pg_stat_user_tables`
 
-Access and usage statistics maintained by postgres on nonsystem tables.
+Access and usage statistics maintained by Postgres on nonsystem tables.
 
-Metrics in this section are reset when a postgres stats reset is issued
+These metrics are reset when a Postgres stats reset is issued
 on the db server.
 
 Derived from the `pg_stat_user_tables` view.
 
-See also `cnp_pg_statio_user_tables`.
+See also [cnp_pg_statio_user_tables](#cnp_pg_statio_user_tables).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -320,8 +316,7 @@ See also `cnp_pg_statio_user_tables`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -331,16 +326,16 @@ as dimensions in Azure Monitor:
 
 ## `cnp_pg_stat_replication`
 
-Realtime information about replication connections to this postgres instance,
-their progress and activity.
+Realtime information about replication connections to this Postgres instance,
+their progress, and their activity.
 
-Metrics in this section are not reset when a postgres stats reset is issued
-on the db server. The "stat" in the name is a historic artefact from postgres
+These metrics aren't reset when a Postgres stats reset is issued
+on the db server. The "stat" in the name is a historic artifact from Postgres
 development.
 
 Derived from the `pg_stat_replication` view.
 
-See also `cnp_pg_replication_slots`, `cnp_pg_replication`.
+See also [cnp_pg_replication_slots](#cnp_pg_statio_user_tables), [cnp_pg_replication](#cnp_pg_replication).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -356,8 +351,7 @@ See also `cnp_pg_replication_slots`, `cnp_pg_replication`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -366,14 +360,14 @@ as dimensions in Azure Monitor:
 
 ## `cnp_pg_statio_user_tables`
 
-I/O activity statistics maintained by postgres on nonsystem tables.
+I/O activity statistics maintained by Postgres on nonsystem tables.
 
-Metrics in this section are reset when a postgres stats reset is issued
+These metrics are reset when a Postgres stats reset is issued
 on the db server.
 
 Derived from the `pg_statio_user_tables` view.
 
-See also `cnp_pg_stat_user_tables`.
+See also [cnp_pg_stat_user_tables](#cnp_pg_stat_user_tables).
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -388,8 +382,7 @@ See also `cnp_pg_stat_user_tables`.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -399,15 +392,15 @@ as dimensions in Azure Monitor:
 
 ## `cnp_pg_settings`
 
-Expose the subset of postgres server settings that can be represented as
-Prometheus compatible metrics–any integer, boolean, or real number.
-Text-format settings, list-valued settings, and enumeration-typed settings are
-not captured or reported.
+Expose the subset of Postgres server settings that can be represented as
+Prometheus compatible metrics—any integer, Boolean, or real number.
+Text-format settings, list-valued settings, and enumeration-typed settings aren't
+captured or reported.
 
-This set of metrics does not expose per-database settings assigned with
+This set of metrics doesn't expose per-database settings assigned with
 `ALTER DATABASE ... SET ...`, per-user settings assigned with `ALTER USER ...
-SET ...`, or per-session values. It shows only the database-system-wide
-global values. You can explore other settings interactively using postgres
+SET ...`, or per-session values. It shows only the database systemwide
+global values. You can explore other settings interactively using Postgres
 system views.
 
 Derived from the `pg_settings` view.
@@ -418,8 +411,7 @@ Derived from the `pg_settings` view.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -448,7 +440,7 @@ Expose the raft status per CNP node of a BDR cluster
 Metrics from pg_catalog.pg_stat_replication_slots for each BDR replication slot.
 These metrics can be used to monitor logical decoding activity and performance the
 sending (upstream) side of a logical replication connection.
-See https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-SLOTS-VIEW
+See [`pg_stat_replication_slots`](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-SLOTS-VIEW)
 for details.
 
 | Metric   | Usage | Description |
@@ -464,8 +456,7 @@ for details.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -475,9 +466,9 @@ as dimensions in Azure Monitor:
 ## `cnp_bdr_rep_lag`
 
 Metrics based on the bdr.node_replication_rates monitoring catalog for monitoring
-BDR replication performance and repliation lag. See
-https://www.enterprisedb.com/docs/pgd/latest/monitoring/#monitoring-outgoing-replication
-and https://www.enterprisedb.com/docs/pgd/latest/bdr/catalogs/#bdrnode_replication_rates
+BDR replication performance and replication lag. See
+[Monitoring Outgoing Replication](/pgd/latest/monitoring/#monitoring-outgoing-replication)
+and [`bdr.node_replication_rates`](/pgd/latest/bdr/catalogs/#bdrnode_replication_rates)
 
 | Metric   | Usage | Description |
 |----------|-------|-------------|
@@ -488,8 +479,7 @@ and https://www.enterprisedb.com/docs/pgd/latest/bdr/catalogs/#bdrnode_replicati
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -514,8 +504,7 @@ WAL retention and the connection status of replication sessions.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -536,8 +525,7 @@ Details are available in the bdr.global_locks view.
 
 
 
-The metrics may have these labels, represented
-as dimensions in Azure Monitor:
+The metrics in this group can have these labels:
 
 | Label | Description |
 |-------|-------------|
@@ -549,18 +537,15 @@ as dimensions in Azure Monitor:
 ## Other metrics streams
 
 In addition to Postgres metrics from the Cloud Native PostgreSQL operator that
-manages databases in BigAnimal, you can stream additional metrics about Kubernetes cluster
+manages databases in BigAnimal, you can stream metrics about Kubernetes cluster
 state and other details to your cloud platform. Any such metrics
 are generally well-known metrics from widely used tools, documented by the
 upstream vendor of the component.
 
-Details on individual metrics from such sources are not listed in this
-document. Refer to the documentation of the tool or project that defines the
-metrics.
-
-See also:
+Refer to the documentation of the tool or project that defines the
+metrics for details on individual metrics.
 
--   [Kubernetes cluster metrics](https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/)
+See also [Kubernetes cluster metrics](https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/).
 
 The cloud platform can supply additional streams of metrics
 directly to your metrics, analytics, and dashboarding endpoint.
diff --git a/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx b/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
index 7f5df57f398..59b1f1aa3f3 100644
--- a/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
+++ b/product_docs/docs/epas/14/epas_upgrade_guide/03_limitations.mdx
@@ -2,7 +2,8 @@
 title: "Upgrade considerations"
 ---
 
-The following limitations apply to upgrading EDB Postgres Advanced Server:
+Consider the following when upgrading EDB Postgres Advanced Server:
+
 
 -   The `pg_upgrade` utility cannot upgrade a partitioned table if a foreign key refers to the partitioned table.
 -   If you are upgrading from the version 9.4 server or a lower version of EDB Postgres Advanced Server, and you use partitioned tables that include a `SUBPARTITION BY` clause, you must use `pg_dump` and `pg_restore` to upgrade an existing EDB Postgres Advanced Server installation to a later version of EDB Postgres Advanced Server. To upgrade, you must:
@@ -11,3 +12,4 @@ The following limitations apply to upgrading EDB Postgres Advanced Server:
     3.  Use `pg_upgrade` to upgrade the rest of the EDB Postgres Advanced Server database to a more recent version.
     4.  Use `pg_restore` to restore the subpartitioned table to the latest upgraded EDB Postgres Advanced Server database.
 -   If you perform an upgrade of the EDB Postgres Advanced Server installation, you must rebuild any hash-partitioned table on the upgraded server.
+-   If you are using an ODBC, JDBC, OCI, or .NET driver to connect to your database applications and upgrading to a new major version of EDB Postgres Advanced Server, upgrade your driver to the latest version when upgrading EDB Postgres Advanced Server.
diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx
index f53f41891cc..934844c75f2 100644
--- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx
+++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx
@@ -17,7 +17,7 @@ Before you begin the installation process:
   ```
 
   !!!note
-  When Replication Server is installed on a machine where Java is not present, the JDK is installed as part of the installation process. Since, in this case, the JDK was installed via Replication Server as its dependency, if you subsequently remove the JDK, Replication Server is also removed.
+  When Replication Server is installed on a machine where Java is not present, the JDK is installed as part of the installation process. Since in this case the JDK was installed via Replication Server as its dependency, if you subsequently remove the JDK, Replication Server is also removed.
 
   If Java 1.8 or greater exists before installing Replication Server, the installed Replication Server is not removed on removal of the JDK.
   !!!
diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png
index fdbaf5d3cfe..4fa23ef94ee 100755
--- a/product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:06b88193e81437e2d6e58e2f2d78498df6148f39ed9af97e4014de0c8b5d78bc
-size 167172
+oid sha256:3061df99dd47ba278dc5446f802c245c4da6c19d2b58d8079ad2ec668092842a
+size 140782
diff --git a/product_docs/docs/ocl_connector/12.1.2.1/images/selecting_the_connectors_installer.png b/product_docs/docs/ocl_connector/12.1.2.1/images/selecting_the_connectors_installer.png
index fb66d12cf3d..28455e738ea 100644
--- a/product_docs/docs/ocl_connector/12.1.2.1/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/ocl_connector/12.1.2.1/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:34c829e958aba00782875a1bf6587ba45c44efc2072033b0b63dbbd4cd87d49d
-size 160720
+oid sha256:96a9540c9fae476178701169ae25a7c1e7f05d63f4f28131b210e67a5e1a09ee
+size 135657
diff --git a/product_docs/docs/ocl_connector/13.1.4.2/images/selecting_the_connectors_installer.png b/product_docs/docs/ocl_connector/13.1.4.2/images/selecting_the_connectors_installer.png
index fb66d12cf3d..b568f787f35 100644
--- a/product_docs/docs/ocl_connector/13.1.4.2/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/ocl_connector/13.1.4.2/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:34c829e958aba00782875a1bf6587ba45c44efc2072033b0b63dbbd4cd87d49d
-size 160720
+oid sha256:0dde0fd854aa15cf06d83dd36c7e059bc81118bdc5d9fd25e72904a79550026e
+size 135647
diff --git a/product_docs/docs/ocl_connector/14.1.0.1/images/selecting_the_connectors_installer.png b/product_docs/docs/ocl_connector/14.1.0.1/images/selecting_the_connectors_installer.png
index fb66d12cf3d..67355eb32a8 100644
--- a/product_docs/docs/ocl_connector/14.1.0.1/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/ocl_connector/14.1.0.1/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:34c829e958aba00782875a1bf6587ba45c44efc2072033b0b63dbbd4cd87d49d
-size 160720
+oid sha256:5d4dc68af55433c0c695eed059160505b3ee6c7d25c7d5426f4228109d84042a
+size 135650
diff --git a/product_docs/docs/odbc_connector/12/images/selecting_the_connectors_installer.png b/product_docs/docs/odbc_connector/12/images/selecting_the_connectors_installer.png
index 457f3f16213..dd0a7847f77 100644
--- a/product_docs/docs/odbc_connector/12/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/odbc_connector/12/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:31f84a8f760ae6e7a2a41bc81b8537906939bc81efd03aca21eed29ae163d796
-size 172259
+oid sha256:ac83549b924c11324930a98efa25864b15c3d5c5e9922e56486b8711e2a09baa
+size 144119
diff --git a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx
index ba88ef72c48..82653f82e55 100644
--- a/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx
+++ b/product_docs/docs/odbc_connector/13/01_odbc_rel_notes/index.mdx
@@ -2,7 +2,7 @@
 title: "Release notes"
 ---
 
-The ODBC JDBC connector documentation describes version 13 of the ODBC JDBC connector. 
+The ODBC JDBC connector documentation describes the latest version of the EDB JDBC connector. 
 
 Release notes describe what's new in a release. When a minor or patch release introduces new functionality, indicators in the content identify the version that introduced the new feature.
 
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx
index bef0c5a20b2..c59d00dcb35 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle.mdx
@@ -37,4 +37,5 @@ Before you begin the installation process:
 
 ```shell
 sudo dnf -y install edb-odbc
+sudo dnf -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx
index 2552e11cc75..f730d12ed4d 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle.mdx
@@ -32,5 +32,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo zypper -n install edb-odbc
+sudo zypper -y install edb-odbc
+sudo zypper -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx
index 93de551134e..27262fe9051 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle.mdx
@@ -31,5 +31,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo zypper -n install edb-odbc
+sudo zypper -y install edb-odbc
+sudo zypper -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx
index 99816d19041..fd81597f8df 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86.mdx
@@ -30,4 +30,5 @@ Before you begin the installation process:
 
 ```shell
 sudo yum -y install edb-odbc
+sudo yum -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx
index 02421591633..c214486a5a8 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86.mdx
@@ -21,6 +21,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo apt-get install edb-odbc
-sudo apt-get install edb-odbc-dev
+sudo apt-get -y install edb-odbc
+sudo apt-get -y install edb-odbc-dev
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx
index 03333330376..c3d3450cdfa 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86.mdx
@@ -21,6 +21,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo apt-get install edb-odbc
-sudo apt-get install edb-odbc-dev
+sudo apt-get -y install edb-odbc
+sudo apt-get -y install edb-odbc-dev
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx
index 6327fe9be39..7721f9b06a5 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86.mdx
@@ -32,4 +32,5 @@ Before you begin the installation process:
 
 ```shell
 sudo dnf -y install edb-odbc
+sudo dnf -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx
index 3ed5633dcbb..600fe99b2ac 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86.mdx
@@ -30,4 +30,5 @@ Before you begin the installation process:
 
 ```shell
 sudo yum -y install edb-odbc
+sudo yum -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx
index 7343c0e578f..0f32a553001 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86.mdx
@@ -35,4 +35,5 @@ Before you begin the installation process:
 
 ```shell
 sudo dnf -y install edb-odbc
+sudo dnf -y install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx
index 7bda3391ea0..85d63705b8d 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86.mdx
@@ -33,4 +33,5 @@ Before you begin the installation process:
 
 ```shell
 sudo zypper -n install edb-odbc
+sudo zypper -n install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx
index 0fe9e0be66b..387a2b5f3b7 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86.mdx
@@ -32,4 +32,5 @@ Before you begin the installation process:
 
 ```shell
 sudo zypper -n install edb-odbc
+sudo zypper -n install edb-odbc-devel
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx
index 9dff1e17a1e..ba2574cd4a6 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86.mdx
@@ -21,6 +21,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo apt-get install edb-odbc
-sudo apt-get install edb-odbc-dev
+sudo apt-get -y install edb-odbc
+sudo apt-get -y install edb-odbc-dev
 ```
diff --git a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx
index 1262f656fd0..e868e76bad4 100644
--- a/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx
+++ b/product_docs/docs/odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86.mdx
@@ -21,6 +21,6 @@ Before you begin the installation process:
 ## Install the package
 
 ```shell
-sudo apt-get install edb-odbc
-sudo apt-get install edb-odbc-dev
+sudo apt-get -y install edb-odbc
+sudo apt-get -y install edb-odbc-dev
 ```
diff --git a/product_docs/docs/odbc_connector/13/images/selecting_the_connectors_installer.png b/product_docs/docs/odbc_connector/13/images/selecting_the_connectors_installer.png
index 457f3f16213..7ec5c51041f 100644
--- a/product_docs/docs/odbc_connector/13/images/selecting_the_connectors_installer.png
+++ b/product_docs/docs/odbc_connector/13/images/selecting_the_connectors_installer.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:31f84a8f760ae6e7a2a41bc81b8537906939bc81efd03aca21eed29ae163d796
-size 172259
+oid sha256:4652dde7f0cb74b4f9430b223363d71b3a6677375351de912c9ab9185f949b42
+size 144147