From cebbc272e72383bcf629c3c372995d55f777635f Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 18 Dec 2024 00:14:57 -0500 Subject: [PATCH] Update website/docs/reference/resource-configs/grants.md --- website/docs/reference/resource-configs/grants.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/grants.md b/website/docs/reference/resource-configs/grants.md index be9918043f..15a920cbbe 100644 --- a/website/docs/reference/resource-configs/grants.md +++ b/website/docs/reference/resource-configs/grants.md @@ -15,7 +15,7 @@ You should define grants as resource configs whenever possible, but you might oc * Apply grants on other database objects besides views and tables. * Create more granular row- and column-level access, use masking policies, or apply future grants. -* Take advantage of more-advanced permission capabilities offered by your data platform, for which dbt does not offer out-of-the-box support using resource configuration. +* Take advantage of more advanced permission capabilities offered by your data platform, for which dbt does not offer out-of-the-box support using resource configuration. * Apply grants in a more complex or custom manner, beyond what the built-in grants capability can provide. For more information on hooks, see [Hooks & operations](/docs/build/hooks-operations).