fixed spacing issue

blog/2024-05-08-gh-actions/gh-actions.qmd

@@ -79,6 +79,7 @@ jobs:
 ```
 
 This workflow includes three top-level elements:
+
 1. `name`: The name of the workflow.
 2. `on`: Specifies the triggers for the workflow, such as `push` and `pull_request` events on the `main` branch.
 3. `jobs`: Lists the jobs that will run, typically in parallel.
@@ -114,6 +115,7 @@ jobs:
 Similar to the linting workflow, this workflow contains the same three top-level elements, but with a different job configuration.
 
 Understanding the components of `jobs:` and their keys was initially confusing. These elements specify the steps to be run in each job, which can be:
+
 - **Shell commands:** Executable commands using the `run:` key, similar to what you would type in a terminal.
 - **Actions:** Reusable actions specified with the `uses:` key, like `actions/checkout@v3` for checking out repository code.
 - **Composite run steps actions:** Grouped steps within a single action for reuse across workflows, specified with the `steps:` key.