Spell check.

src/cookbooks/data_modeling/using_aggregates.md

@@ -102,7 +102,6 @@ Looker's PDTs and aggregate awareness are _only_ referenced in Looker when at le
 - The metric requires strict change control.
 - A scheduled alert is required in case of failure or data out of sync. Airflow sends emails and alerts on failure for BigQuery aggregate tables, which are addressed daily by the Data Engineering team during the Airflow Triage.
 - The table will be queried directly or used as a source for other analysis. Looker PDTs are not designed to be queried directly.
-- The query requires full flexibility to use DML, data types, aggregation functions and different types of JOIN.
 
 #### A Materialized View is suitable when:
 
@@ -118,7 +117,7 @@ Looker's PDTs and aggregate awareness are _only_ referenced in Looker when at le
 
 #### A Looker PDT is suitable when:
 
-- Your goal is to improve the performance and query response in Dashboards by pre-aggregating common query patterns and not having to re-create the dashboard Everytime the base table changes.
+- Your goal is to improve the performance and query response in dashboards by pre-aggregating common query patterns and not having to re-create the dashboard every time the base table changes.
 - The results can be based on shredded data (tables with client_id).
 - Change control is not required or is already implemented in the base table. This can be verified by looking for the label `change_controlled: true` in the metadata.
 - A scheduled alert on failure is _not_ required. Failures must be monitored in the [PDT Admin Dashboard](https://mozilla.cloud.looker.com/admin/pdts) or in the [Errors and Broken Content Dashboard](https://mozilla.cloud.looker.com/dashboards/system__activity::errors_and_broken_content).