From 183d4e2cf035378be39154ea3a212ab7a7f572ca Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Wed, 23 Oct 2024 14:45:48 +0100
Subject: [PATCH] Update
 website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md

---
 .../docs/docs/cloud/connect-data-platform/connnect-bigquery.md   | 1 -
 1 file changed, 1 deletion(-)

diff --git a/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md b/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
index 6a38c94b535..cad4862fd3c 100644
--- a/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
+++ b/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
@@ -91,7 +91,6 @@ The `location` of BigQuery datasets can be set using the `location` setting in a
 
 When a `maximum_bytes_billed` value is configured for a BigQuery profile, that allows you to limit how much data your query can process. It’s a safeguard to prevent your query from accidentally processing more data than you expect, which could lead to higher costs. Queries executed by dbt will fail if they exceed the configured maximum bytes threshhold. This configuration should be supplied as an integer number of bytes.
 
-```jinja
 
 my-profile:
   target: dev