For-Developers/Guides/How-to-set-up-a-beta.md

@@ -3,6 +3,7 @@ This is a guide and process guidance on how to conduct a beta.
 > **Note:** These instructions required that your GitLab account be provisioned as a developer. If you aren't a developer yet, please fill out the "Developer Request Form" at the [Help Desk](https://gitlab.deterrencedispensed.com/deterrence-dispensed/help-desk/-/issues)
 
 # Configuring your GitLab for a beta
+
 The steps below will configure your GitLab repository for a beta. Your files will NOT be exposed to anyone who is not a member of your project (either explicitly added by you, or within your group).
 
 1. Go to your repository settings, then "General".
@@ -10,10 +11,11 @@ The steps below will configure your GitLab repository for a beta. Your files wil
 3. Ensure Repository is enabled, but "Only Project Members"
 4. Ensure "Forks" under "Repository" is set to "Only Project Members"
 5. Under Repository, disable "Pipelines", "Container Registry", and "Packages".
-5. Disable Analytics, Wiki, Snippets, and Operations. (Unless you wish to use these features)
-6. Click "Save Changes".
+6. Disable Analytics, Wiki, Snippets, and Operations. (Unless you wish to use these features)
+7. Click "Save Changes".
 
 # Preparing for a beta
+
 _These instructions presume you are using GitLab for version control._
 
 1. Commit your files. You must have the following files in your package as highlighted in the [Release Package Requirements](https://gitlab.deterrencedispensed.com/deterrence-dispensed/information-and-tutorials/-/wikis/For-Developers/Resources/Release-Package-Requirements) guidance document.
@@ -22,14 +24,17 @@ _These instructions presume you are using GitLab for version control._
 4. Upload your file to the beta channel.
 
 # Configuring the beta channel
+
 > **Note:** This step can only be done by a RocketChat administrator.
 
 1. Create a channel with the following format: `#beta.username_projectslug`
 2. Populate the description and topic.
-> Description: `Beta channel for project`
-> Topic: `Beta channel for project`
+
+> Description: `Beta channel for project` Topic: `Beta channel for project`
+
 3. Paste in the beta rules as described below:
-```
+
+```plaintext
 **BETA RULES**
 The Purpose:
 To create a singular publicly released and shared package of known good files paired with instructions that would enable someone to build whatever we have released without having to come in contact with us.
@@ -44,13 +49,14 @@ The Rules:
 
 Info:
 GitLab Link for submitting issues: <insert link>
-
 ```
+
 4. Drop in the beta files archive.
 5. Set the designer as the Channel Owner.
 6. Add channel to #z.beta, with note if beta is public or private.
 7. Update private channel link directory with non-expiring permanent beta invite.
 
 # Pro-tips:
+
 - An announcement can be updated to display a persistent message in the channel, and can be found in its channel settings.
 - It's strongly, **STRONGLY** recommended that you do not include source files (STEPs, Natives) in your beta.
\ No newline at end of file