From 3778e9a255f785740a6b50e354a4d56a5a2f45b8 Mon Sep 17 00:00:00 2001 From: Chris Charlton Date: Fri, 28 Jun 2024 19:16:13 -0700 Subject: [PATCH] Fixed formatting of "Updating" and "Adding" sections The individual portions of text were colliding together. The markdown source seems to originally try to show them in a listed form so I added bullets. Minor formatting updates as well. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 8d31883..74149be 100644 --- a/README.md +++ b/README.md @@ -36,13 +36,13 @@ workflows: Note that if you want to hook onto deploy workflows, you'll need to deploy your `pantheon.yml` into an environment first. Likewise, if you are adding new operations or changing the script an operation will target, the deploy which contains those adjustments to `pantheon.yml` will not self-referentially exhibit the new behavior. Only subsequent deploys will be affected. **When Updating:** -**pantheon.yml**: Updates will fire on the next sequential workflow, not post-deploy. -**scripts**: Updates will fire post-deploy. -**script location**: Updates will fire on next sequential workflow, not post-deploy. +- **`pantheon.yml`**: Updates will fire on the next sequential workflow, not post-deploy. +- **scripts**: Updates will fire post-deploy. +- **script location**: Updates will fire on next sequential workflow, not post-deploy. **When Adding:** -**pantheon.yml**: Updates will fire on the next sequential workflow, not post-deploy. -**scripts**: Updates will fire on the next sequential workflow. +- **`pantheon.yml`**: Updates will fire on the next sequential workflow, not post-deploy. +- **scripts**: Updates will fire on the next sequential workflow. ## Security ##