edit packaging specification for correctness and organization

site/source/service-packaging/build-package-example/05_create-manifest.rst

@@ -209,11 +209,11 @@ And populate it with the following example manifest (see the line comments for a
             entrypoint: compat 
             # Arguments to pass into the entrypoint executable. In this example, the full command run will be: `compat duplicity hello-world /mnt/backup /root/data`
             args: 
-            - duplicity
-            - hello-world
-            - /mnt/backup
-            # For duplicity, the backup mount point needs to be something other than `/root`, so we default to `/root/data`
-            - /root/data
+              - duplicity
+              - hello-world
+              - /mnt/backup
+              # For duplicity, the backup mount point needs to be something other than `/root`, so we default to `/root/data`
+              - /root/data
             mounts:
                 # BACKUP is the default volume that is used for backups. This is whatever backup drive is mounted to the device, or a network filesystem.  
                 # The value here donates where the mount point will be. The backup drive is mounted to this location.
@@ -226,10 +226,10 @@ And populate it with the following example manifest (see the line comments for a
             system: true
             entrypoint: compat
             args:
-            - duplicity
-            - hello-world
-            - /root/data
-            - /mnt/backup
+              - duplicity
+              - hello-world
+              - /root/data
+              - /mnt/backup
             mounts:
                 BACKUP: "/mnt/backup"
                 main: "/root"
@@ -239,10 +239,10 @@ And populate it with the following example manifest (see the line comments for a
         name: Hello World Action
         description: A description that describes what the action will accomplish.
         warning: |
-        A warning message indicating and potential dangers associated with the action
+          A warning message indicating and potential dangers associated with the action
         # Indicates what state the service can be in while executing the action
         allowed-statuses:
-        - running
+          - running
         # Defines how the action is run
         implementation:
             type: docker

site/source/service-packaging/build-package-example/09_create-wrapper.rst

@@ -4,7 +4,9 @@
 Step 9 - Create Wrapper Repo
 ============================
 
-In order for the Start9 team to review your package for submission to the Start9 Marketplace, we ask that you create a wrapper repository for the project and its components. Let's do that for our hello-world service.
+In order for the Start9 team to review your package for submission to the Start9 Marketplace, we ask that you create a wrapper repository for the project and its components. This repo should contain everything you need to build the service.
+
+Let's do that for our hello-world service.
 
 For a quick start convenience, Start9 has made the finalized version of the `hello-world-wrapper <https://github.com/Start9Labs/hello-world-wrapper>`_ available as a *GitHub template*. Clicking "Use this template" in that repository will clone the entire contents to a specified location. Each file will still have to be manually edited to reflect the changes necessary for your service.
 

site/source/service-packaging/build-package-example/resources.rst

@@ -16,6 +16,11 @@ When you have built and tested your project for EmbassyOS, please send Start9 a
 
 If you are deploying to an alternative marketplace, please shout it out in our community channels!
 
+Additional Options
+------------------
+
+Properties - TODO
+
 References
 ----------