diff --git a/docs/release_notes/v-1.4.md b/docs/release_notes/v-1.4.md
index 0663edbc83b8..e735ca4ad274 100644
--- a/docs/release_notes/v-1.4.md
+++ b/docs/release_notes/v-1.4.md
@@ -8,17 +8,27 @@ Platform changes improve Airbyte for everyone with a self-managed instance.
 
 ### Configure the schema refresh rate
 
-Use the new environment variable, `DISCOVER_REFRESH_WINDOW_MINUTES`, to set how often Airbyte refreshes schemas, in minutes. The default is once per day in self-managed instances. The maximum is once per minute. Set this to 0 to disable automatic schema refreshes. [Learn more about configuring Airbyte](../operator-guides/configuring-airbyte.md).
+Before starting a sync, Airbyte can run discovery to refresh schemas. However, running discovery has a performance cost. For large databases with thousands of tables, discovery can take a while, and it might not be necessary before every sync.
+
+Use the new environment variable, `DISCOVER_REFRESH_WINDOW_MINUTES`, to set the minimum number of minutes Airbyte will wait to refresh a schema. By setting a larger number, you delay automatic schema refreshes and improve sync performance. The default in self-managed instances is 1440 (once per day). The lowest interval you can set is 1 (once per minute).
+
+```yml title="values.yaml"
+worker:
+  env_vars:
+    DISCOVER_REFRESH_WINDOW_MINUTES: 1440 # Airbyte automatically refreshes schemas no more than once per day (1440 minutes).
+```
+
+ Set this to 0 to disable automatic schema refreshes.
 
 ```yml title="values.yaml"
 worker:
   env_vars:
-    DISCOVER_REFRESH_WINDOW_MINUTES: 1440
+    DISCOVER_REFRESH_WINDOW_MINUTES: 0 # Airbyte does not automatically detect schema changes.
 ```
 
 ### Connectors support custom image registries
 
-Connectors can now use custom image registries rather than Airbyte’s public Docker registry. If you configure Airbyte to use a custom image registry, it now automatically uses that registry for connector images as well. Previously, only platform images supported this. In this example, we set Airbyte’s `values.yaml` file to pull all images from GitHub.
+Connectors can now use custom image registries rather than Airbyte’s public Docker registry. If you configure Airbyte to use a custom image registry, it now automatically uses that registry for connector images as well as platform images. Previously, only platform images supported this. In this example, we set Airbyte’s `values.yaml` file to pull all images from GitHub.
 
 ```yml title="values.yaml"
 global:
@@ -26,11 +36,9 @@ global:
     registry: ghcr.io/NAMESPACE
 ```
 
-[Learn how to set up custom image registries](../deploying-airbyte/integrations/custom-image-registries).
+You must ensure copies of platform and connector images are available in your custom image registry. [Learn how to set up custom image registries](../deploying-airbyte/integrations/custom-image-registries).
 
-:::note
-If you have custom internal connectors that specify an image using a fully qualified domain name (for example, `example.com/airbyte/source-postgres`), Airbyte ignores your configured image registry and pulls images from the domain specified by that connector.
-:::
+[Custom Docker connectors](../operator-guides/using-custom-connectors/) in your workspace that specify an image using a fully qualified domain name (for example, `example.com/airbyte/your-custom-source`) ignore your configured custom image registry and pull images from the domain specified by that connector.
 
 ### Reduced resource consumption
 
@@ -44,7 +52,7 @@ To learn more about Airbyte Self-Managed Enterprise, [talk to our sales team](ht
 
 We are excited to share that Self-Managed Enterprise now supports audit logging. This initial release focuses on providing you with full visibility into permission changes. This data will ensure you have records of any unauthorized changes and insider threats, making it easy to continue meeting your compliance obligations while using Airbyte.
 
-Audit logging requires you to configure Airbyte to read from and write to a blob storage solution (S3, GCS, Azure Blob Storage). This is configured in Airbyte’s `values.yaml` file. To enable audit logging, add the following environment variables:
+Audit logging requires you to configure a blob storage solution (S3, GCS, Azure Blob Storage). Then, configure Airbyte to read from and write to it with Airbyte’s `values.yaml` file. To enable audit logging, add the following environment variables:
 
 ```yml title="values.yaml"
 server: