Add or fix initial descriptions of each article.

configuration/configuring-date-and-time/en.md

@@ -1,7 +1,7 @@
 # Configuring Date and time
 
-{{< altimg "configuring-date-and-time.jpg" "help-center/configuration/configuring-date-and-time/" >}}
-
 You can configure the date and time of your system by going to the Budgie Menu, opening the Settings app then going to the Date & Time section.
 
+{{< altimg "configuring-date-and-time.jpg" "help-center/configuration/configuring-date-and-time/" >}}
+
 You will be presented with the following window. This window provides you the ability to enable / disable automatic date & time, automatic time zone changing, and the time format.

installation/disks/en.md

@@ -1,6 +1,6 @@
 # Disks
 
-Solus provides multiple ways you can install onto your system:
+Solus provides multiple ways you can install onto your system.
 
 1. Solus can take up the entire drive.
 2. You can install Solus next to your existing operating system, such as Windows. *If you have multiple operating systems 

installation/preparing-to-install/en.md

@@ -1,9 +1,9 @@
 # Preparing to installation
 
-## Getting the ISO
-
 The first step to installing Solus is acquiring the correct media. The Solus Project provides ISO images, which contain the contents of the Solus for installing.
 
+## Getting the ISO
+
 You can download a Solus ISO by going to our [Download page](https://solus-project.com/download).
 
 ---

packaging/building-a-package/en.md

@@ -1,5 +1,7 @@
 ## Building a Package
 
+This guide will walk you through setting up the file(s), tooling, and building your package.
+
 ### Setting up Packager file 
 
 In order to utilise the build system, you must first set up a configuration file that has your packager details.

packaging/package.yml/en.md

@@ -1,8 +1,10 @@
-## Package.yml
+# Package.yml
+
+All packages consist of a single build file, which provides all of the required metadata for the package manager, plus the build steps involved to produce a package. This follows the YAML specification.
 
 ### Format 
 
-All packages consist of a single build file, which provides all of the required metadata for the package manager, plus the build steps involved to produce a package. This follows the YAML specification, thus all `package.yml` files **must** be valid YAML.
+All `package.yml` files **must** be valid YAML.
 
 As can be seen in the example below, the file is organised into a key->value hierarchy. Some values may be required to be in a list format, whereas most are simple strings. The build step sections are all considered optional, however if you do not 
 perform *any* steps, then no package is generated. Each of these keys contains content that will be placed within a script and executed within a controlled environment to perform the package build. To all intents and purposes, they are bash scripts