Apply suggestions from code review

Co-authored-by: Casie Oxford <[email protected]>

Author: forstisabella

src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md

@@ -59,4 +59,4 @@ To set up Databricks as your Reverse ETL source:
 > Segment previously supported token-based authentication, but now uses OAuth (M2M) authentication at the recommendation of Databricks.
 > If you previously set up your source using token-based authentication, Segment will continue to support it. If you want to create a new source or update the connection settings of an existing source, Segment only supports [OAuth machine-to-machine (M2M) authentication](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}.
 
-Once you've successfully added your Databricks source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. 
+After you've successfully added your Databricks source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. 

src/connections/reverse-etl/system.md

@@ -23,7 +23,7 @@ Reverse ETL computes the incremental changes to your data directly within your d
 > info "Delete Records Payload"
 > The only value passed for deleted records is its unique ID which can be accessed as `__segment_id`. 
 
-In order for Segment to compute the data changes within your warehouse, Segment needs to have both read and write permissions to the warehouse schema table. At a high level, the extract process requires read permissions for the query being executed. Segment keeps track of changes to the query results through tables that Segment manages in a dedicated schema (for example, `_segment_reverse_etl`), which requires some write permissions.
+For Segment to compute the data changes within your warehouse, Segment needs to have both read and write permissions to the warehouse schema table. At a high level, the extract process requires read permissions for the query being executed. Segment keeps track of changes to the query results through tables that Segment manages in a dedicated schema (for example, `_segment_reverse_etl`), which requires some write permissions.
 
 > warning ""
 > There may be cost implications to having Segment query your warehouse tables.