From e31608f7609989d68ddec11a0d8a613587987e92 Mon Sep 17 00:00:00 2001
From: goodroot <9484709+goodroot@users.noreply.github.com>
Date: Mon, 22 Jul 2024 13:03:31 -0700
Subject: [PATCH] remove bad links

---
 clients/ingest-rust.md | 2 +-
 introduction.md        | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/clients/ingest-rust.md b/clients/ingest-rust.md
index 86ddcc859..ed6f40d1d 100644
--- a/clients/ingest-rust.md
+++ b/clients/ingest-rust.md
@@ -180,7 +180,7 @@ transaction. For this to work, your buffer must contain data that targets only
 one table. This is because QuestDB doesn't support multi-table transactions.
 
 In order to ensure in advance that a flush will be transactional, 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 transactional.
 
 ### When to choose the TCP transport?
diff --git a/introduction.md b/introduction.md
index 887d9bf17..c7e0c1190 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