Added more imperative language to instructional headers

README.md

@@ -14,7 +14,7 @@ There are a collection of procedures to follow for proper execution and installa
 
 Make sure to configure things like the website's name, author, etc., via the `${SUKAATO_SITE_SOURCE_ROOT}/site.toml` file.
 
-#### Supplying Resources to Themes
+#### Supply Resources to Themes
 
 Make sure that subdirectories under path `${SUKAATO_SITE_SOURCE_ROOT}/priv/static/` are appropriately populated. Either follow the active/enabled theme's CSS/SASS path references, or change such path references to match custom `${SUKAATO_SITE_SOURCE_ROOT}/priv/static` prefixed filepaths.
 
@@ -36,7 +36,7 @@ The website has a default theme supplied, but you are welcome to make your own a
 > [!TIP]
 > Make sure that all renderable stylesheet paths for files under `${SUKAATO_SITE_SOURCE_ROOT}/lib/sukaato_web/controllers/page_*/` are set to `/assets/app.css`, or a path relative to `${SUKAATO_SITE_SOURCE_ROOT}/priv/static` that has been made external (whether the directory exists yet or not). Again, see about [asset management in Phoenix web framework](https://hexdocs.pm/phoenix/asset_management.html#images-fonts-and-external-files).
 
-### Running this project's server
+### Runn the project's server
 
 This project was built using the Phoenix web framework. To start the Phoenix server:
 
@@ -47,7 +47,7 @@ This project was built using the Phoenix web framework. To start the Phoenix ser
 
 Now you can visit [`localhost:4001`](https://localhost:4001) from your browser.
 
-### Running this project in production
+### Run this project in production
 
 Ready to run in production? Please [check Phoenix web framework's deployment guides](https://hexdocs.pm/phoenix/deployment.html).