Merge pull request #501 from getsolus/pkg-inclusion-formatting

docs/packaging: Fix formatting issue in package-inclusion.md

docs/packaging/procedures/package-inclusion.md

@@ -27,8 +27,8 @@ This policy sets forth the criteria for a package to be accepted for inclusion i
 - DOA (dead-on-arrival) packages are generally rejected from Solus. However, they may be included at the discretion of the project, if they provide unique functionality.
 - Projects with no tags/tarballs which lack traction, may be frozen until a suitable release is made. Tagging releases is an indicator for good release engineering practices.
 - Typically, we prefer **stable** tagged releases. However, this may be waived if:
-- The software has significant traction (i.e. prerelease)
-- A bug fix only exists beyond the latest stable release for a git source
+    - The software has significant traction (i.e. prerelease)
+    - A bug fix only exists beyond the latest stable release for a git source
 
 ### Stack Complexity