From 8eb63d69e48b370ea43b700d0c52f32e3cb32adc Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Wed, 23 Oct 2024 14:46:23 +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 b6867878b15..24b06ac929c 100644
--- a/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
+++ b/website/docs/docs/cloud/connect-data-platform/connnect-bigquery.md
@@ -92,7 +92,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.
 
 
-  target: dev
   outputs:
     dev:
       type: bigquery