diff --git a/docs/reference/components/applications.md b/docs/reference/components/applications.md
index 0bde610c..2af170bf 100644
--- a/docs/reference/components/applications.md
+++ b/docs/reference/components/applications.md
@@ -39,6 +39,7 @@ Alternatively, to mimic interfacing with a hosted Harper instance, use operation
      package=<path-to-project> \
      restart=true
    ```
+
    - Make sure to omit the `target` option so that it _deploys_ to the Harper instance running locally
    - The `package=<path-to-project>` option creates a symlink to the application simplifying restarts
      - By default, the `deploy` operation command will _deploy_ the current directory by packaging it up and streaming the bytes. By specifying `package`, it skips this and references the file path directly
diff --git a/versioned_docs/version-4.4/developers/components/managing.md b/versioned_docs/version-4.4/developers/components/managing.md
index 8b8d03cc..97402e39 100644
--- a/versioned_docs/version-4.4/developers/components/managing.md
+++ b/versioned_docs/version-4.4/developers/components/managing.md
@@ -37,6 +37,7 @@ Alternatively, to mimic interfacing with a hosted Harper instance, use operation
      package=<path-to-project> \
      restart=true
    ```
+
    - Make sure to omit the `target` option so that it _deploys_ to the Harper instance running locally
    - The `package=<path-to-project>` option creates a symlink to the component simplifying restarts
      - By default, the `deploy_component` operation command will _deploy_ the current directory by packaging it up and streaming the bytes. By specifying `package`, it skips this and references the file path directly
diff --git a/versioned_docs/version-4.5/developers/components/managing.md b/versioned_docs/version-4.5/developers/components/managing.md
index 8b8d03cc..97402e39 100644
--- a/versioned_docs/version-4.5/developers/components/managing.md
+++ b/versioned_docs/version-4.5/developers/components/managing.md
@@ -37,6 +37,7 @@ Alternatively, to mimic interfacing with a hosted Harper instance, use operation
      package=<path-to-project> \
      restart=true
    ```
+
    - Make sure to omit the `target` option so that it _deploys_ to the Harper instance running locally
    - The `package=<path-to-project>` option creates a symlink to the component simplifying restarts
      - By default, the `deploy_component` operation command will _deploy_ the current directory by packaging it up and streaming the bytes. By specifying `package`, it skips this and references the file path directly
diff --git a/versioned_docs/version-4.6/reference/components/applications.md b/versioned_docs/version-4.6/reference/components/applications.md
index 0bde610c..2af170bf 100644
--- a/versioned_docs/version-4.6/reference/components/applications.md
+++ b/versioned_docs/version-4.6/reference/components/applications.md
@@ -39,6 +39,7 @@ Alternatively, to mimic interfacing with a hosted Harper instance, use operation
      package=<path-to-project> \
      restart=true
    ```
+
    - Make sure to omit the `target` option so that it _deploys_ to the Harper instance running locally
    - The `package=<path-to-project>` option creates a symlink to the application simplifying restarts
      - By default, the `deploy` operation command will _deploy_ the current directory by packaging it up and streaming the bytes. By specifying `package`, it skips this and references the file path directly