update known issues

Author: mpfuster

advocacy_docs/supported-open-source/warehousepg/wem/overview/known_issues.mdx

@@ -6,18 +6,29 @@ description: Learn about known issues in WarehousePG Enterprise Manager version
 
 These are the currently known issues and limitations identified in the WarehousePG Enterprise Manager (WEM) release. Where applicable, we have included workarounds to help you mitigate the impact of these issues. These issues are actively tracked and are planned for resolution in a future release.
 
-- **RHEL 7 deployment:** WEM is not supported for installation on Red Hat Enterprise Linux 7 (RHEL 7). This limitation applies only to where the WEM application itself is deployed; WEM is fully capable of monitoring WarehousePG (WHPG) clusters that are running on RHEL 7 nodes.
+### Deployment & infrastructure
+
+- WEM cannot be installed on Red Hat Enterprise Linux 7. Note that this restriction applies only to the host running the WEM application; WEM is fully capable of monitoring WHPG clusters running on RHEL 7 nodes.
+[PTT-703]: #
+- Running WHPG and WEM on the same host using the same database is not supported. WEM writes its application state into the `observability` database; sharing this environment can lead to configuration conflicts and upgrade complexity.
+[PTT-714]: # 
+- The maximum Postgres connection pool size is currently hardcoded to 5. There is currently no mechanism to scale or configure this limit via environment variables.
+
+### Backup management
+
 [PTT-723]: #
-- Currently, the functionality provided in the **Backups** panel is only supported if WEM is running on the WHPG coordinator.
+- The **Backups** panel is only supported when WEM is installed directly on the WHPG coordinator node.
 [PTT-682]: #
-- The **Find Table** tab in the **Backup** panel is not fully functional.
-[PTT-703]: #
-- Running WHPG and WEM on the same host and using the same database is not supported, as WEM application state is written into the WHPG observability database that is intended to be read-only, which can lead to misconfiguration and upgrade complexity.
+- The **Find Table** search tab within the **Backup** panel is currently non-functional.
+[PTT-697]: #
+- The **Backup** panel may incorrectly display a `gpbackup_history.db not found` error if the system contains no existing backups. This message can be ignored if no backups have been performed.
+
+### Query editor
+
 [PTT-712]: #
-- There is currently an issue where **Query Editor** becomes irresponsive when running multiple queries. This issue is under investigation and will be fixed soon.
-[PTT-714]: # 
-- The maximum Postgres connection pool size is currently hardcoded to 5, with no way to configure or scale it via environment or external settings.
+- The **Query Editor** may become unresponsive when executing multiple concurrent queries. This issue is under active investigation.
+
+### Data analysis
+
 [PTT-701]: #
-- The tables in the **Data Analysis** panel have a hardcoded minimum size filter which causes WEM to fail to display small tables.
-[PTT-697]: #
-- The **Backup** panel incorrectly displays an error: `gpbackup_history.db not found` when there are no existing backups. 
+- Tables in the **Data Analysis** panel are subject to a hardcoded minimum size filter. Tables falling below this threshold will not be displayed in the interface.