Swap out level 300 png for svg

Signed-off-by: Dj Walker-Morgan <[email protected]>

advocacy_docs/edb-postgres-ai/analytics/concepts.mdx

@@ -122,4 +122,4 @@ Here's a slightly more comprehensive diagram of how these services fit together:
 
 Here's the more detailed, zoomed-in view of "what's in the box":
 
-[![Level 200 Architecture](images/level-300.svg)](images/level-300.svg)
+[![Level 300 Architecture](images/level-300.svg)](images/level-300.svg)

advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx

@@ -44,7 +44,7 @@ in object storage.
 
 Here's what's in the box of a Lakehouse node:
 
-![Level 300 Architecture of Postgres Lakehouse node](./images/level-300-architecture.png)
+[![Level 300 Architecture](images/level-300.svg)](images/level-300.svg)
 
 ## Getting started
 
@@ -100,7 +100,7 @@ cluster). Then you can copy the connection string and use it as an argument to
 
 In general, you should be able to connect to the database with any Postgres
 client. We expect all introspection queries to work, and if you find one that
-does not, then that is a bug.
+doesn't, then that's a bug.
 
 ### Understand the constraints
 
@@ -128,11 +128,11 @@ see [Reference - Bring your own data](./reference/#advanced-bring-your-own-data)
 
 ## Inspect the benchmark datasets
 
-Inspect the Benchmark Datasets.  Every cluster has some benchmarking data
+Inspect the Benchmark Datasets. Every cluster has some benchmarking data
 available out of the box. If you are using pgcli, you can run `\dn` to see
 the available tables.
 
-The available benchmarking datsets are:
+The available benchmarking datasets are:
 
 * TPC-H, at scale factors 1, 10, 100 and 1000
 * TPC-DS, at scale factors 1, 10, 100 and 1000