From f465eb865b96524bf857d455d0170b45f2ff30a7 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 3 Nov 2023 12:13:28 +0000
Subject: [PATCH] Update
website/docs/reference/resource-configs/pre-hook-post-hook.md
---
website/docs/reference/resource-configs/pre-hook-post-hook.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/website/docs/reference/resource-configs/pre-hook-post-hook.md b/website/docs/reference/resource-configs/pre-hook-post-hook.md
index 0d8df81aa24..f48b65b4ad6 100644
--- a/website/docs/reference/resource-configs/pre-hook-post-hook.md
+++ b/website/docs/reference/resource-configs/pre-hook-post-hook.md
@@ -181,7 +181,9 @@ There may be occasions where you need to run these hooks _outside_ of a transact
* You want to run a `VACUUM` in a `post-hook`, however, this cannot be executed within a transaction ([Redshift docs](https://docs.aws.amazon.com/redshift/latest/dg/r_VACUUM_command.html#r_VACUUM_usage_notes))
* You want to insert a record into an audit at the start of a run and do not want that statement rolled back if the model creation fails.
-To achieve this behavior, you can use one of the following syntaxes. (Important Note: Do not use this syntax if you are using a database where dbt does not use transactions by default. This includes databases like Snowflake, BigQuery, and Spark or Databricks.)
+To achieve this behavior, you can use one of the following syntaxes.
+
+Important note: Do not use this syntax if you are using a database where dbt does not use transactions by default. This includes databases like Snowflake, BigQuery, and Spark or Databricks.