Fix code blocks in docs

Author: edongashi

README.md

@@ -28,7 +28,9 @@ every session start for restricted users. This can be accomplished by configurin
 For example, to automatically load the `pg_diffix` extension for all users connecting to a database,
 you can execute the following command:
 
-`ALTER DATABASE db_name SET session_preload_libraries TO 'pg_diffix';`
+```
+ALTER DATABASE db_name SET session_preload_libraries TO 'pg_diffix';
+```
 
 Once loaded, the extension logs information to `/var/log/postgresql/postgresql-13-main.log` or equivalent.
 
@@ -42,7 +44,9 @@ You might also need to remove the extension from the list of preloaded libraries
 
 For example, to reset the list of preloaded libraries for a database, you can execute the following command:
 
-`ALTER DATABASE db_name SET session_preload_libraries TO DEFAULT;`
+```
+ALTER DATABASE db_name SET session_preload_libraries TO DEFAULT;
+```
 
 ## Testing the extension
 
@@ -61,7 +65,10 @@ or if available, just make your usual PostgreSQL user a `SUPERUSER`.
 
 Or you can use the [PGXN Extension Build and Test Tools](https://github.com/pgxn/docker-pgxn-tools) Docker image:
 
-`docker run -it --rm --mount "type=bind,src=$(pwd),dst=/repo" pgxn/pgxn-tools sh -c 'cd /repo && apt update && apt install -y jq && pg-start 13 && pg-build-test'`.
+```
+docker run -it --rm --mount "type=bind,src=$(pwd),dst=/repo" pgxn/pgxn-tools sh -c \
+  'cd /repo && apt update && apt install -y jq && pg-start 13 && pg-build-test'
+```
 
 ## Docker images
 
@@ -76,15 +83,21 @@ The example below shows how to build the image and run a minimally configured co
 
 Build the image:
 
-`make image`
+```
+make image
+```
 
 Run the container in foreground and expose in port 10432:
 
-`docker run --rm --name pg_diffix -e POSTGRES_PASSWORD=postgres -p 10432:5432 pg_diffix`
+```
+docker run --rm --name pg_diffix -e POSTGRES_PASSWORD=postgres -p 10432:5432 pg_diffix
+```
 
 From another shell you can connect to the container via `psql`:
 
-`psql -h localhost -p 10432 -d postgres -U postgres`
+```
+psql -h localhost -p 10432 -d postgres -U postgres
+```
 
 For more advanced usage see the [official image reference](https://hub.docker.com/_/postgres).
 
@@ -102,16 +115,25 @@ Three users are created, all of them with password `demo`:
 
 Build the image:
 
-`make demo-image`
+```
+make demo-image
+```
 
 Run the container in foreground and expose in port 10432:
 
-`docker run --rm --name pg_diffix_demo -e POSTGRES_PASSWORD=postgres -e BANKING_PASSWORD=demo -p 10432:5432 pg_diffix_demo`
+```
+docker run --rm --name pg_diffix_demo -e POSTGRES_PASSWORD=postgres -e BANKING_PASSWORD=demo -p 10432:5432 pg_diffix_demo
+```
 
 Connect to the banking database (from another shell) for anonymized access:
 
-`psql -h localhost -p 10432 -d banking -U trusted_user`
+```
+psql -h localhost -p 10432 -d banking -U trusted_user
+```
 
 To keep the container running you can start it in detached mode and with a restart policy:
 
-`docker run -d --name pg_diffix_demo --restart unless-stopped -e POSTGRES_PASSWORD=postgres -e BANKING_PASSWORD=demo -p 10432:5432 pg_diffix_demo`
+```
+docker run -d --name pg_diffix_demo --restart unless-stopped \
+  -e POSTGRES_PASSWORD=postgres -e BANKING_PASSWORD=demo -p 10432:5432 pg_diffix_demo
+```

docs/admin_guide.md

@@ -36,7 +36,7 @@ Trusted users have fewer SQL restrictions than untrusted users, and therefore ha
 
 For example, the command to assign the access level `anonymized_untrusted` to the role `public_access` is:
 
-```SQL
+```
 CALL diffix.mark_role('public_access', 'anonymized_untrusted');
 ```
 
@@ -69,12 +69,12 @@ __NOTE:__ if AID columns are not correctly labeled, the extension may fail to an
 The procedure `diffix.mark_personal(table_name, aid_columns...)` is used to label a table as personal and
 to label its AID columns. For example:
 
-```SQL
+```
 CALL diffix.mark_personal('employee_info', 'employee_id');
 ```
 labels the table `employee_info` as personal, and labels the `employee_id` column as an AID column.
 
-```SQL
+```
 CALL diffix.mark_personal('transactions', 'sender_acct', 'receiver_acct');
 ```
 labels the table `transactions` as personal, and labels the `sender_acct` and `receiver_acct` columns as AID columns.
@@ -186,7 +186,7 @@ Given that AIDs may not be perfect, some care must be taken in the selection of
 
 For example, imagine the following query in a table where `account_number` is the AID column:
 
-```sql
+```
 SELECT last_name, religion, count(*)
 FROM table
 GROUP BY last_name, religion

docs/admin_tutorial.md

@@ -8,52 +8,70 @@ containing a column named `id`, which uniquely identifies protected entities (th
 
 ## Installation
 
-1. Install the packages required for building the extension:
+1\. Install the packages required for building the extension:
 
-`sudo apt-get install make jq gcc postgresql-server-dev-14`
+```
+sudo apt-get install make jq gcc postgresql-server-dev-14
+```
 
-2. Install PGXN Client tools:
+2\. Install PGXN Client tools:
 
-`sudo apt-get install pgxnclient`
+```
+sudo apt-get install pgxnclient
+```
 
-3. Install the extension:
+3\. Install the extension:
 
-`sudo pgxn install pg_diffix`
+```
+sudo pgxn install pg_diffix
+```
 
 ## Activation
 
-1. Connect to the database as a superuser:
+1\. Connect to the database as a superuser:
 
-`sudo -u postgres psql test_db`
+```
+sudo -u postgres psql test_db
+```
 
-2. Activate the extension for the current database:
+2\. Activate the extension for the current database:
 
-`CREATE EXTENSION pg_diffix;`
+```
+CREATE EXTENSION pg_diffix;
+```
 
-3. Automatically load the extension for all users connecting to the database:
+3\. Automatically load the extension for all users connecting to the database:
 
-`ALTER DATABASE test_db SET session_preload_libraries TO 'pg_diffix';`
+```
+ALTER DATABASE test_db SET session_preload_libraries TO 'pg_diffix';
+```
 
 ## Configuration
 
-1. Label the test data as personal (requiring anonymization):
+1\. Label the test data as personal (requiring anonymization):
 
-`CALL diffix.mark_personal('test_table', 'id');`
+```
+CALL diffix.mark_personal('test_table', 'id');
+```
 
-2. Create an account for the analyst:
+2\. Create an account for the analyst:
 
-`CREATE USER analyst_role WITH PASSWORD 'some_password';`
+```
+CREATE USER analyst_role WITH PASSWORD 'some_password';
+```
 
-3. Give the analyst read-only access to the test database:
+3\. Give the analyst read-only access to the test database:
 
 ```
 GRANT CONNECT ON DATABASE test_db TO analyst_role;
 GRANT SELECT ON ALL TABLES IN SCHEMA public TO analyst_role;
 ```
 
-4. Label the analyst as restricted and trusted:
+4\. Label the analyst as restricted and trusted:
 
-`CALL diffix.mark_role('analyst_role', 'anonymized_trusted');`
+```
+CALL diffix.mark_role('analyst_role', 'anonymized_trusted');
+```
 
 
 __That's it!__ The analyst can now connect to the database and issue (only) anonymizing queries against the test dataset.