update docs

docs/website/docs/dlt-ecosystem/destinations/bigquery.md

@@ -125,6 +125,8 @@ recreated with a [clone command](https://cloud.google.com/bigquery/docs/table-cl
 The loader follows [Google recommendations](https://cloud.google.com/bigquery/docs/error-messages) when retrying and terminating jobs.
 The Google BigQuery client implements an elaborate retry mechanism and timeouts for queries and file uploads, which may be configured in destination options.
 
+BigQuery destination also supports [streaming insert](https://cloud.google.com/bigquery/docs/streaming-data-into-bigquery). The mode provides better performance with small (<500 records) batches, but it buffers the data, preventing any update/delete operations on it. Due to this, streaming inserts are only available with `write_disposition="append"`, and the inserted data is blocked for editing for up to 90 min (reading, however, is available immediately). [See more](https://cloud.google.com/bigquery/quotas#streaming_inserts).
+
 ## Supported File Formats
 
 You can configure the following file formats to load data to BigQuery:
@@ -244,6 +246,10 @@ bigquery_adapter(
 
 # Apply table level options.
 bigquery_adapter(event_data, table_description="Dummy event data.")
+
+# Load data in "streaming insert" mode (only available with
+# write_disposition="append").
+bigquery_adapter(event_data, insert_api="streaming")
 ```
 
 In the example above, the adapter specifies that `event_date` should be used for partitioning and both `event_date` and `user_id` should be used for clustering (in the given order) when the table is created.