From 5559238287304a682d310e72c4961ad1422a7496 Mon Sep 17 00:00:00 2001 From: josegonzalez Date: Tue, 15 Nov 2022 16:32:57 -0500 Subject: [PATCH] docs: fix embedded lists on deployment tasks --- docs/advanced-usage/deployment-tasks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/advanced-usage/deployment-tasks.md b/docs/advanced-usage/deployment-tasks.md index b6d75dc90..f1c71d51c 100644 --- a/docs/advanced-usage/deployment-tasks.md +++ b/docs/advanced-usage/deployment-tasks.md @@ -26,8 +26,8 @@ Each "phase" has different expectations and limitations: - When to use: This should be used in conjunction with external systems to signal the completion of your deploy. - Are changes committed to the image at this phase: No - Example use-cases - - Notifying slack that your app is deployed - - Coordinating traffic routing with a central load balancer + - Notifying slack that your app is deployed + - Coordinating traffic routing with a central load balancer - `app.json`: `scripts.postdeploy` - When to use: This should be used when you wish to run a command _once_, after the app is created and not on subsequent deploys to the app. - Are changes committed to the image at this phase: No