freshness is a config now, not a property

website/docs/reference/configs-and-properties.md

@@ -17,8 +17,7 @@ A rule of thumb: properties declare things _about_ your project resources; confi
 For example, you can use resource **properties** to:
 * Describe models, snapshots, seed files, and their columns
 * Assert "truths" about a model, in the form of [data tests](/docs/build/data-tests), e.g. "this `id` column is unique"
-* Define pointers to existing tables that contain raw data, in the form of [sources](/docs/build/sources), and assert the expected "freshness" of this raw data
-* Define official downstream uses of your data models, in the form of [exposures](/docs/build/exposures)
+* Define official downstream uses of your data models, in the form of [exposures](/docs/build/exposures), and assert an exposure's "type"
 
 Whereas you can use **configurations** to:
 * Change how a model will be materialized (<Term id="table" />, <Term id="view" />, incremental, etc)

website/docs/reference/define-properties.md

@@ -37,7 +37,7 @@ These properties are:
 - [`deprecation_date`](/reference/resource-properties/deprecation_date)
 - [`description`](/reference/resource-properties/description)
 - [`quote`](/reference/resource-properties/columns#quote)
-- [`source` properties](/reference/source-properties) (for example, `loaded_at_field`, `freshness`)
+- [`source` properties](/reference/source-properties) (for example, `loaded_at_field`)
 - [`exposure` properties](/reference/exposure-properties) (for example, `type`, `maturity`)
   - Note that while most exposure properties must be configured directly in `properties.yml` files, you can set the [`enabled`](/reference/resource-configs/enabled) config at the [project level](/reference/exposure-properties#project-level-configs) in the`dbt_project.yml` file.
 - [`macro` properties](/reference/macro-properties) (for example, `arguments`)