Update changelog & readme

CHANGELOG.md

@@ -6,21 +6,22 @@
 - Updated variables used to determine if engagements are enabled in `hubspot__contacts` to also check variable `hubspot_engagement_contact_enabled`.
 
 ## Features
-- The following changes stem from changes made in the source package. See the [source package CHANGELOG](https://github.com/fivetran/dbt_hubspot_source/blob/main/CHANGELOG.md) for more details. 
+- The following changes stem from changes made in the source package. See the [source package v0.14.0 CHANGELOG entry](https://github.com/fivetran/dbt_hubspot_source/blob/main/CHANGELOG.md#dbt_hubspot_source-v0140) for more details. 
 
 - Added the following staging models, along with documentation and tests:
   - `stg_hubspot__property`
   - `stg_hubspot__property_option`
-  - These tables can be disabled by setting `hubspot_property_enabled': False` in your dbt_project.yml vars. See [Step 4 of the README](https://github.com/fivetran/dbt_hubspot_#step-4-disable-models-for-non-existent-sources) for more details. 
+  - These tables can be disabled by setting `hubspot_property_enabled: False` in your dbt_project.yml vars. See [Step 4 of the README](https://github.com/fivetran/dbt_hubspot#step-4-disable-models-for-non-existent-sources) for more details. 
 
 - When including a passthrough `property_hs_*` column, you now have the option to include the corresponding, human-readable label in the staging models. 
   - The above-mentioned `property` tables are required for this feature. If you do not have them and have to disable them, unfortunately you will not be able to use this feature.
-  - See the [Adding property label section](https://github.com/fivetran/dbt_hubspot#adding-property-label) of the README for instructions on how to enable this feature! 
+  - See the [Adding property label section](https://github.com/fivetran/dbt_hubspot#adding-property-label) of the README for more details on how to enable this feature! 
+  - We recommend being selective with the label columns you add. As you add more label columns, your run time will increase due to the underlying logic requirements.
   - This update applies to models:
-    - `hubspot__company`
-    - `hubspot__contact`
-    - `hubspot__deal`
-    - `hubspot__ticket` 
+    - `hubspot__companies`
+    - `hubspot__contacts`
+    - `hubspot__deals`
+    - `hubspot__tickets` 
 
 # dbt_hubspot v0.14.0
 

README.md

@@ -144,6 +144,7 @@ vars:
   hubspot_engagement_note_enabled: false
   hubspot_engagement_task_enabled: false
   hubspot_owner_enabled: false
+  hubspot_property_enabled: false                         # Disables property and property_option tables
   
   # Service
   hubspot_service_enabled: true                           # Enables all service/ticket models. Default = false
@@ -204,7 +205,7 @@ For `property_hs_*` columns, you can enable the corresponding, human-readable `p
 #### Important! 
 - You must have sources `property` and `property_option` enabled to enable labels. By default, these sources are enabled.  
 - You CANNOT enable labels if using `hubspot__pass_through_all_columns: true`.` 
-- As you add more label columns, your run time will increase due to the underlying logic requirements.
+- We recommend being selective with the label columns you add. As you add more label columns, your run time will increase due to the underlying logic requirements.
 
 To enable labels for a given property, set the property attribute `add_property_label: true`, using the below format.