diff --git a/clients/ingest-rust.md b/clients/ingest-rust.md
index f1313b330..2a2c16114 100644
--- a/clients/ingest-rust.md
+++ b/clients/ingest-rust.md
@@ -175,7 +175,7 @@ As described at the [ILP overview](/docs/reference/api/ilp/overview#http-transac
 the HTTP transport has some support for transactions.
 
 In order to ensure in advance that a flush will not affect more than one table, call
-[`sender.flush_and_keep_with_flags(&mut buffer, true)`](Sender::flush_and_keep_with_flags).
+`sender.flush_and_keep_with_flags(&mut buffer, true)`.
 This call will refuse to flush a buffer if the flush wouldn't be data-transactional.
 
 
diff --git a/introduction.md b/introduction.md
index fc2f7c2da..aec0c1d0a 100644
--- a/introduction.md
+++ b/introduction.md
@@ -80,6 +80,10 @@ infrastructure sprawl.
   title="Benchmark results for QuestDB 7.3.10, InfluxDB 2.7.4 and Timescale 2.14.2"
 />
 
+```sql title='yo' demo='https://example.com'
+SQL
+```
+
 With a specialized [time-series database](/glossary/time-series-database/), you
 don't need to worry about out-of-order data, duplicates, exactly one semantics,
 frequency of ingestion, or the many other details you will find in real-time