catalog-backend: update description of disableRelationsCompatibility post testing

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>

.changeset/curly-teachers-marry.md

@@ -2,4 +2,4 @@
 '@backstage/plugin-catalog-backend': minor
 ---
 
-Added a new `catalog.disableRelationsCompatibility` configuration option that avoids JSON deserialization and serialization if possible when reading entities. This can significantly improve the overall performance of the catalog, but it removes the backwards compatibility processing that ensures that both `entity.relation[].target` and `entity.relation[].targetRef` are present in returned entities.
+Added a new `catalog.disableRelationsCompatibility` configuration option that avoids JSON deserialization and serialization if possible when reading entities. This significantly reduces the memory usage of the catalog, and slightly increases performance, but it removes the backwards compatibility processing that ensures that both `entity.relation[].target` and `entity.relation[].targetRef` are present in returned entities.

plugins/catalog-backend/config.d.ts

@@ -142,9 +142,9 @@ export interface Config {
      * Disables the compatibility layer for relations in returned entities that
      * ensures that all relations objects have both `target` and `targetRef`.
      *
-     * Enabling this option can very significantly improve the performance of
-     * the catalog, but may break consumers that rely on the existence of
-     * `target` in the relations objects.
+     * Enabling this option significantly reduces the memory usage of the
+     * catalog, and slightly increases performance, but may break consumers that
+     * rely on the existence of `target` in the relations objects.
      */
     disableRelationsCompatibility?: boolean;