update changelog and readme

CHANGELOG.md

@@ -1,7 +1,7 @@
 # dbt_amazon_ads v0.3.0
 [PR #11](https://github.com/fivetran/dbt_amazon_ads/pull/11) includes the following updates:
 ## Feature update 🎉
-- Unioning capability! This adds the ability to union source data from multiple amazon_ads connectors. Refer to the [README](https://github.com/fivetran/dbt_amazon_ads/blob/main/README.md) for more details.
+- Unioning capability! This adds the ability to union source data from multiple amazon_ads connectors. Refer to the [Union Multiple Connectors README section](https://github.com/fivetran/dbt_amazon_ads/blob/main/README.md#union-multiple-connectors) for more details.
 
 ## Under the hood 🚘
 - In the source package, updated tmp models to union source data using the `fivetran_utils.union_data` macro. 

README.md

@@ -76,8 +76,6 @@ vars:
 ```
 
 ## (Optional) Step 5: Additional configurations
-<details><summary>Expand for configurations</summary>
-
 ### Union multiple connectors
 If you have multiple amazon_ads connectors in Fivetran and would like to use this package on all of them simultaneously, we have provided functionality to do so. The package will union all of the data together and pass the unioned table into the transformations. You will be able to see which source it came from in the `source_relation` column of each model. To use this functionality, you will need to set either the `amazon_ads_union_schemas` OR `amazon_ads_union_databases` variables (cannot do both) in your root `dbt_project.yml` file:
 
@@ -134,8 +132,6 @@ If an individual source table has a different name than the package expects, add
 vars:
     amazon_ads_<default_source_table_name>_identifier: your_table_name 
 ```
-</details>
-
 ## (Optional) Step 6: Orchestrate your models with Fivetran Transformations for dbt Core™    
 <details><summary>Expand for more details</summary>