diff --git a/sites/docs/pages/components/all-components/index.md b/sites/docs/pages/components/all-components/index.md
index 594c1f4b97..f8f2336ba3 100644
--- a/sites/docs/pages/components/all-components/index.md
+++ b/sites/docs/pages/components/all-components/index.md
@@ -342,19 +342,6 @@ description:  An index of the components available in the Evidence library.
     </div>
 </Grid>
 
-### [Mixed Type Charts](/components/charts/mixed-type-charts)
-
-<Grid>
-    <div class="border rounded-lg p-4 my-2 mx-1 hover:shadow-md transition">
-        <b>Bar and Line</b>
-        <a href="/components/charts/mixed-type-charts">
-    
-        <img src="/img/bar-line.png" alt="bar-line" class="markdown">
-    
-        </a>
-    </div>
-</Grid>
-
 ### [Annotations](/components/charts/annotations)
 
 <Grid>
diff --git a/sites/docs/pages/core-concepts/queries/index.md b/sites/docs/pages/core-concepts/queries/index.md
index 9c0a715d65..d76a4712e3 100644
--- a/sites/docs/pages/core-concepts/queries/index.md
+++ b/sites/docs/pages/core-concepts/queries/index.md
@@ -10,6 +10,18 @@ Evidence runs markdown code fences as SQL queries. These queries use the [DuckDB
 
 If you have a data source called `needful_things`, you run a query against it like this:
 
+<DocTab defaultTab='code'>
+    <div slot='preview'>
+
+```sql sales_by_category
+select 
+  category, sum(sales) as sales
+from needful_things.orders
+group by 1
+```
+
+    </div>
+
 ````markdown
 ```sql sales_by_category
 select 
@@ -18,6 +30,7 @@ from needful_things.orders
 group by 1
 ```
 ````
+</DocTab>
 
 When you open a page in dev mode, Evidence runs all of the queries on the page. In dev mode, Evidence monitors the contents of your SQL blocks, and reloads the page as necessary to reflect any changes you've made to your queries.
 
@@ -71,8 +84,7 @@ from (
 
 ### View Compiled SQL
 
-You can choose whether you want to see the compiled or written SQL inside the query viewer:
-![compiled-written-toggle](/img/compiled-written-toggle.gif)
+You can choose whether you want to see the compiled or written SQL inside the query viewer.
 
 ### Ordering and Circular References
 
@@ -80,9 +92,7 @@ The order that queries appear on the page doesn't matter to the SQL compiler. Yo
 
 Some SQL dialects require sub-queries to be aliased, including Postgres and MySQL. E.g. `from ${sales_by_item} as sales_by_item`.
 
-The SQL compiler detects circular and missing references. If a query includes either a circular reference or a missing reference, Evidence will display an error that looks like a syntax error in a normal SQL query. Queries with compiler errors are not sent to your database.
-
-![circular-error-single](/img/circular-error-single.png)
+The SQL compiler detects circular and missing references. 
 
 ## SQL File Queries
 
diff --git a/sites/docs/static/img/bar-line.png b/sites/docs/static/img/bar-line.png
deleted file mode 100644
index 580d8cce79..0000000000
Binary files a/sites/docs/static/img/bar-line.png and /dev/null differ
diff --git a/sites/docs/static/img/compiled-written-toggle.gif b/sites/docs/static/img/compiled-written-toggle.gif
deleted file mode 100644
index c9b1ce0898..0000000000
Binary files a/sites/docs/static/img/compiled-written-toggle.gif and /dev/null differ