Feature: Add Quickstart Model Counts to README

CHANGELOG.md

@@ -1,3 +1,8 @@
+# dbt_stripe_source version.version
+
+## Documentation
+- Corrected references to connectors and connections in the README. ([#88](https://github.com/fivetran/dbt_stripe_source/pull/88))
+
 # dbt_stripe_source v0.12.1
 
 ## Feature Updates

README.md

@@ -28,7 +28,7 @@
 ### Step 1: Prerequisites
 To use this dbt package, you must have the following:
 
-- At least one Fivetran stripe connector syncing data into your destination.
+- At least one Fivetran stripe connection syncing data into your destination.
 - A **BigQuery**, **Snowflake**, **Redshift**, **Databricks**, or **PostgreSQL** destination.
 
 #### Databricks Dispatch Configuration
@@ -72,8 +72,8 @@ vars:
 ### (Optional) Step 5: Additional configurations
 <details open><summary>Expand to view configurations</summary>
 
-#### Unioning Multiple Stripe Connectors
-If you have multiple Stripe connectors you would like to use this package on simultaneously, we have added the ability to do so. Data from disparate connectors will be unioned together and be passed downstream to the end models. The `source_relation` column will specify where each record comes from. To use this functionality, you will need to either set the `stripe_union_schemas` or `stripe_union_databases` variables. Please also make sure the single-source `stripe_database` and `stripe_schema` variables are removed.
+#### Unioning Multiple Stripe Connections
+If you have multiple Stripe connections you would like to use this package on simultaneously, we have added the ability to do so. Data from disparate connections will be unioned together and be passed downstream to the end models. The `source_relation` column will specify where each record comes from. To use this functionality, you will need to either set the `stripe_union_schemas` or `stripe_union_databases` variables. Please also make sure the single-source `stripe_database` and `stripe_schema` variables are removed.
 
 ```yml
 # dbt_project.yml
@@ -100,11 +100,11 @@ vars:
 ```
 
 #### Leveraging Subscription Vs Subscription History Sources
-For Stripe connectors set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connector then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table.
+For Stripe connections set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connection then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table.
 > **Please note that if you have `stripe__using_subscription_history` enabled then the package will filter for only active records.**
 ```yml
 vars:
-    stripe__using_subscription_history: False  # True by default. Set to False if your connector syncs the `subscription` table instead. 
+    stripe__using_subscription_history: False  # True by default. Set to False if your connection syncs the `subscription` table instead. 
 ```
 
 #### Running on Live vs Test Customers