diff --git a/src/mas/devops/data/catalogs/v9-260924-amd64.yaml b/src/mas/devops/data/catalogs/v9-260924-amd64.yaml
index 25c8c988..373bb53d 100644
--- a/src/mas/devops/data/catalogs/v9-260924-amd64.yaml
+++ b/src/mas/devops/data/catalogs/v9-260924-amd64.yaml
@@ -215,6 +215,6 @@ editorial:
     - IBM Maximo Real Estate and Facilities [v9.1.15](https://www.ibm.com/support/pages/node/7288833) and [v9.2.3](https://www.ibm.com/support/pages/node/7289065)
     - IBM Maximo AI Service [v9.1.19](https://www.ibm.com/support/pages/node/7287754) and [v9.2.3](https://www.ibm.com/support/pages/node/7287755)
     - IBM Suite License Service v3.13.2
-    - Mongo: 8.0.30
+    - 'Mongo: 8.0.30'
   known_issues:
-    - title: 
+    - title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
diff --git a/src/mas/devops/data/catalogs/v9-260924-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260924-ppc64le.yaml
index 8f4004b3..a7f59302 100644
--- a/src/mas/devops/data/catalogs/v9-260924-ppc64le.yaml
+++ b/src/mas/devops/data/catalogs/v9-260924-ppc64le.yaml
@@ -75,6 +75,6 @@ editorial:
     - IBM Maximo Application Suite Core Platform [v9.0.32](https://www.ibm.com/support/pages/node/7289766), [v9.1.26](https://www.ibm.com/support/pages/node/7289767) and [v9.2.7](https://www.ibm.com/support/pages/node/7289768)
     - IBM Maximo Manage [v9.0.32](https://www.ibm.com/support/pages/node/7289352),[v9.1.25](https://www.ibm.com/support/pages/node/7289351) and [v9.2.4](https://www.ibm.com/support/pages/node/7289350)
     - IBM Suite License Service v3.13.2
-    - Mongo: 8.0.30
+    - 'Mongo: 8.0.30'
   known_issues:
-    - title: 
+    - title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
diff --git a/src/mas/devops/data/catalogs/v9-260924-s390x.yaml b/src/mas/devops/data/catalogs/v9-260924-s390x.yaml
index d952303a..3e056de6 100644
--- a/src/mas/devops/data/catalogs/v9-260924-s390x.yaml
+++ b/src/mas/devops/data/catalogs/v9-260924-s390x.yaml
@@ -75,7 +75,7 @@ editorial:
     - IBM Maximo Application Suite Core Platform [v9.0.32](https://www.ibm.com/support/pages/node/7289766), [v9.1.26](https://www.ibm.com/support/pages/node/7289767) and [v9.2.7](https://www.ibm.com/support/pages/node/7289768)
     - IBM Maximo Manage [v9.0.32](https://www.ibm.com/support/pages/node/7289352),[v9.1.25](https://www.ibm.com/support/pages/node/7289351) and [v9.2.4](https://www.ibm.com/support/pages/node/7289350)
     - IBM Suite License Service v3.13
-    - Mongo: 8.0.30
+    - 'Mongo: 8.0.30'
   known_issues:
-    - title: 
+    - title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
     
\ No newline at end of file