docs: Fix inconsistencies in documentation

docs/ADMIN_API.md

@@ -6,7 +6,7 @@ The admin API is used to manage namespaces on a `sqld` instance. Namespaces are
 
 To enable the admin API, and manage namespaces, two extra flags need to be passed to `sqld`:
 
-- `--admin-listen-addr <addr>:<port>`: the address and port on which the admin API should listen. It must be different from the user API listen address (whi defaults to port 8080).
+- `--admin-listen-addr <addr>:<port>`: the address and port on which the admin API should listen. It must be different from the user API listen address (which defaults to port 8080).
 - `--enable-namespaces`: enable namespaces for the instance. By default namespaces are disabled.
 
 ## Routes

docs/DOCKER.md

@@ -17,7 +17,7 @@ docker run --name some-sqld-replica -p 8081:8080 -ti \
     -e SQLD_NODE=replica \
     -e SQLD_PRIMARY_URL=https://<host>:<port> \
     ghcr.io/tursodatabase/libsql-server:latest
-````
+```
 
 ## Running on Apple Silicon
 
@@ -122,7 +122,6 @@ inter-node communication. Recommended to leave this on default.
 Simple docker compose for local development:
 
 ```yaml
-version: "3"
 services:
   db:
     image: ghcr.io/tursodatabase/libsql-server:latest

docs/USER_GUIDE.md

@@ -25,6 +25,7 @@ Welcome to the `sqld` user guide!
 The `sqld` program provides libsql over HTTP and supports transparent replication.
 
 ![libsql cluster overview.](sqld-overview.png)
+
 <p align="center">
 Figure 1. Overview of libsql clustering.
 </p>
@@ -82,7 +83,7 @@ You now have a `sqld` primary server listening to SQL over HTTP at `127.0.0.1:80
 
 ### Launching a replica server
 
-To start a a `sqld` server in replica mode, run:
+To start a `sqld` server in replica mode, run:
 
 ```console
 sqld \
@@ -150,7 +151,7 @@ curl -X POST -d '{"statements": ["select * from testme"]}' $YOUR_APP.fly.dev
 ```
 
 ```json
-[{"b":2,"a":1,"c":3}]
+[{ "b": 2, "a": 1, "c": 3 }]
 ```
 
 ## Incremental snapshots
@@ -182,7 +183,7 @@ and then configure `sqld` to generate an incremental snapshot every 5 seconds an
 sqld --snapshot-exec ./snapshot.sh --max-log-duration 5
 ```
 
-When you write to the `sqld` database, you will eventually see log line such as:
+When you write to the `sqld` database, you will eventually see a log line such as:
 
 ```console
 2023-08-11T08:21:04.183564Z  INFO sqld::replication::snapshot: snapshot `e126f594-90f4-45be-9350-bc8a01160de9-0-2.snap` successfully created
@@ -254,7 +255,7 @@ For example, if you have the following entries in your `/etc/hosts` file:
 127.0.0.1       db2.local
 ```
 
-You can access `db1` with the `http://db1.local:8080`URL and `db2` with `http://db2.local:8080`.
+You can access `db1` with the `http://db1.local:8080` URL and `db2` with `http://db2.local:8080`.
 The database files for the databases are stored in `<data dir>/dbs/db1` and `<data dir/dbs/db2`, respectively.
 
 ### Path based routing

libsql-server/perf/pgbench/README.md

@@ -4,7 +4,7 @@ Setup database:
 
 ```console
 psql -h 127.0.0.1 -p 5432 < pg_bench_schema.sql
-````
+```
 
 Run `pgbench`:
 

libsql-sqlite3/doc/testrunner.md

@@ -158,7 +158,7 @@ If there is no permutation, the individual test script may be run with:
   ./testfixture $PATH_TO_SCRIPT
 ```
 
-Or, if the failure occured as part of a permutation:
+Or, if the failure occurred as part of a permutation:
 
 ```
   ./testfixture $TESTDIR/testrunner.tcl $PERMUTATION $PATH_TO_SCRIPT