From bfeec20c146f12aab6bc15db5377b95a2004dfd9 Mon Sep 17 00:00:00 2001
From: Daniel Bachhuber <daniel.bachhuber@automattic.com>
Date: Thu, 29 Jun 2023 15:23:37 -0700
Subject: [PATCH] wp-now: Clean up the README a bit (#85)

From https://github.com/WordPress/playground-tools/pull/82
---
 packages/wp-now/README.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/packages/wp-now/README.md b/packages/wp-now/README.md
index 674a23f6f2..85b7e8212d 100644
--- a/packages/wp-now/README.md
+++ b/packages/wp-now/README.md
@@ -68,13 +68,13 @@ Of these, `wp-now php` currently supports the `--path=<path>` and `--php=<versio
 
 ## Using Blueprints
 
-Blueprints are JSON files with a list of steps to execute after starting wp-now. They can be used to automate the setup of a WordPress site, including defining wp-config constants, installing plugins, themes, and content.
+Blueprints are JSON files with a list of steps to execute after starting wp-now. They can be used to automate the setup of a WordPress site, including defining wp-config constants, installing plugins, themes, and content. [Learn more about Blueprints.](https://wordpress.github.io/wordpress-playground/blueprints-api/index)
 
-## Defining a custom URL
+### Defining Custom URLs
 
-Here is an example of a blueprint that defines custom URL constant. `wp-now` will automatically detect the blueprint and execute it after starting the server. In consequence, the site will be available at `http://myurl.wpnow`. Make sure myurl.wpnow is added to your hosts file.
+Here is an example of a Blueprint that defines custom URL constant. `wp-now` will automatically detect the blueprint and execute it after starting the server. In consequence, the site will be available at `http://myurl.wpnow`. Make sure myurl.wpnow is added to your hosts file.
 
-To execute this blueprint, create a file named `blueprint-example.json` and run `wp-now start --blueprint=path/to/blueprint-example.json`. Note that the `virtualize` is set to `true` to avoid modifying the `wp-config.php` file that is shared between all the projects.
+To execute this Blueprint, create a file named `blueprint-example.json` and run `wp-now start --blueprint=path/to/blueprint-example.json`. Note that the `virtualize` is set to `true` to avoid modifying the `wp-config.php` file that is shared between all the projects.
 
 ```json
 {
@@ -113,7 +113,7 @@ The Blueprint to listen on port `80` will look like this:
 }
 ```
 
-## Debugging
+### Defining Debugging Constants
 
 In the similar way we can define `WP_DEBUG` constants and read the debug logs.
 
@@ -135,7 +135,9 @@ Run `wp-now start --blueprint=path/to/blueprint-example.json` where `blueprint-e
 ```
 
 This will enable the debug logs and will create a `debug.log` file in the `~/wp-now/wp-content/${project}/debug.log` directory.
+
 If you prefer to set a custom path for the debug log file, you can set `WP_DEBUG_LOG` to be a directory. Remember that the `php-wasm` server runs udner a VFS (virtual file system) where the default documentRoot is always `/var/www/html`.
+
 For example, if you run `wp-now start --blueprint=path/to/blueprint-example.json` from a theme named `atlas` you could use this directory: `/var/www/html/wp-content/themes/atlas/example.log` and you will find the `example.log` file in your project directory.
 
 ```json