From 81de9ebdc06ee0087f9270f8995743e9f887db0a Mon Sep 17 00:00:00 2001
From: Jared Hoover <98363870+jhadobe@users.noreply.github.com>
Date: Wed, 12 Jun 2024 16:48:35 -0500
Subject: [PATCH] Apply suggestions from code review

---
 src/pages/events/commands.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/pages/events/commands.md b/src/pages/events/commands.md
index 52bffd18..292c8f4c 100644
--- a/src/pages/events/commands.md
+++ b/src/pages/events/commands.md
@@ -136,9 +136,9 @@ The `events:metadata:populate` command creates event metadata based on XML and a
 
 Event metadata is automatically created for new event subscriptions when you run the [`events:subscribe` command](#subscribe-to-an-event) and synchronize events registered in `io_events.xml` files or `config.php` when the `setup:upgrade` command runs. In the following situations, we recommend creating event metadata using the `events:metadata:populate` command:
 
--  You have configured an event provider after an `io_events.xml` file was pushed to your cloud instance and a redeployment has not occurred since this change.
--  You have not run `setup:upgrade` since adding an `io_events.xml` file to your on-premise instance.
--  You manually edited the event subscriptions configuration in `app/etc/config.php`.
+* You have configured an event provider after an `io_events.xml` file was pushed to your cloud instance and a redeployment has not occurred since this change.
+* You have not run `setup:upgrade` since adding an `io_events.xml` file to your on-premise instance.
+* You manually edited the event subscriptions configuration in `app/etc/config.php`.
 
 ### Usage