diff --git a/CHANGELOG.md b/CHANGELOG.md
index 88521ba..4f9911e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,8 @@
+# dbt_iterable_source version.version
+
+## Documentation
+- Corrected references to connectors and connections in the README. ([#41](https://github.com/fivetran/dbt_iterable_source/pull/41))
+
 # dbt_iterable_source v0.10.0
 [PR #39](https://github.com/fivetran/dbt_iterable_source/pull/39) contains the following updates:
 
diff --git a/README.md b/README.md
index d64ad4f..9ea1d32 100644
--- a/README.md
+++ b/README.md
@@ -27,12 +27,12 @@
 ### Step 1: Prerequisites
 To use this dbt package, you must have the following:
 
-- At least one Fivetran Iterable connector syncing data into your destination.
+- At least one Fivetran Iterable connection syncing data into your destination.
 - A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
 
 ##### Unsubscribe tables are no longer history tables
 
-For connectors created past August 2023, the `user_unsubscribed_channel_history` and `user_unsubscribed_message_type_history` Iterable objects will no longer be history tables as part of schema changes following Iterable's API updates. The fields have also changed. There is no lift required, since we have checks in place that will automatically persist the respective fields depending on what exists in your schema (they will still be history tables if you are using the old schema).
+For connections created past August 2023, the `user_unsubscribed_channel_history` and `user_unsubscribed_message_type_history` Iterable objects will no longer be history tables as part of schema changes following Iterable's API updates. The fields have also changed. There is no lift required, since we have checks in place that will automatically persist the respective fields depending on what exists in your schema (they will still be history tables if you are using the old schema).
 
 *Please be sure you are syncing them as either both history or non-history.*
 
@@ -58,7 +58,7 @@ vars:
 
 ### Step 4: Enabling/Disabling Models
 
-Your Iterable connector might not sync every table that this package expects. If your syncs exclude certain tables, it is either because you do not use that functionality in Iterable or have actively excluded some tables from your syncs. In order to enable or disable the relevant tables in the package, you will need to add the following variable(s) to your `dbt_project.yml` file.
+Your Iterable connection might not sync every table that this package expects. If your syncs exclude certain tables, it is either because you do not use that functionality in Iterable or have actively excluded some tables from your syncs. In order to enable or disable the relevant tables in the package, you will need to add the following variable(s) to your `dbt_project.yml` file.
 
 By default, all variables are assumed to be `true`.