Added Base Development Tools section to Package Management Basics. Added more specification of languages

across various code blocks.

configuration/modifying-grub/en.md

@@ -38,7 +38,7 @@ There are some circumstances in which updating Solus could fail to update its GR
 4. Once found, replace the "sdX#" in the following command with the partition and mount to the target directory we created: `mount /dev/sdX# /target`
 5. Next we will mount several other directories:
 
-```
+``` bash
 mount --bind /proc /target/proc
 mount --bind /dev /target/dev
 mount --bind /sys /target/sys

gaming/minecraft/en.md

@@ -24,7 +24,8 @@ sudo gedit /usr/share/applications/minecraft.desktop
 ```
 
 Paste in the following and save it:
-```
+
+``` ini
 [Desktop Entry]
 Version=1.0
 Type=Application

package-management/basics/en.md

@@ -91,3 +91,13 @@ sudo eopkg search documents
 ```
 
 Notice that you don't need to search for a specific software name, although you can do that. We search summaries and software names by default.
+
+## Base Development Tools
+
+If you are wanting to compile software under Solus, we recommend installing our system.devel component by running the following:
+
+``` bash
+sudo eopkg install -c system.devel
+```
+
+This will provide items such as clang, gcc, make, a multitude of devel sub-packages, and more. Our system.devel is similar to packages on other operating systems, such as Debian's build-essentials.

packaging/building-a-package/en.md

@@ -12,7 +12,7 @@ In order to utilise the build system, you must first set up a configuration file
 This file lives in the `.solus` folder of your home directory. You will need to create the `.solus` folder as well as the inner `packager` file. Inside the packager file, you need two keys, `Name` and `Email`. This is used when generating the machine 
 file so that the packager details are stored within the resulting binary package.
 
-``` conf
+``` ini
 Name=Your Name Here
 Email=your.email@address
 ```

packaging/package.yml/en.md

@@ -202,7 +202,7 @@ A YAML list (or array) can be expressed in multiple ways. A short array-notation
 
 They can also be expressed like this:
 
-```
+``` yaml
 - First Value
 - Second Value
 - Third Value
@@ -229,14 +229,14 @@ An explicit key, usually a sub-package name:
 
 A mix of both:
 
-```
+``` yaml
 - somevalue
 - somekey: another value
 ```
 
 The values may also be expressed in list form, still using the same default key logic:
 
-```
+``` yaml
 - [one,two, three]
 - somekey: [one,two, three]
 - key:

packaging/packaging-practices/en.md

@@ -158,7 +158,7 @@ may use the explicit package name. Always ensure you select the correct package,
 
 In the `builddeps` list, simply use the `pkgconfig(name)` syntax. For example, to add gtk+-3.0 to the build dependencies, we would do the following:
 
-```
+``` yaml
 builddeps:
     - pkgconfig(gtk+-3.0)
 ```
@@ -184,7 +184,7 @@ pkgconfig(gtk+-wayland-3.0) pkgconfig(gtk+-x11-3.0)
 
 As may be obvious, simply list the package name. Note we discourage this when a `pkgconfig` dependency is available.
 
-```
+``` yaml
 builddeps:
     - stk-devel
 ```

software/java/en.md

@@ -17,7 +17,7 @@ Grab the Java Runtime Environment (JRE) as `.tar.gz` from the [Oracle Download P
 
 Extract JRE and move it to /opt:
 
-```
+``` bash
 cd ~/Downloads
 tar xf jre-8u121-linux-x64.tar.gz
 sudo mv jre1.8.0_121 /opt/
@@ -26,7 +26,7 @@ sudo ln -svf /opt/jre1.8.0_121/bin/java /usr/bin/java
 
 To enable Java in Firefox:
 
-```
+``` bash
 mkdir -p ~/.mozilla/plugins
 ln -s /opt/jre1.8.0_121/lib/amd64/libnpjp2.so ~/.mozilla/plugins/libnpjp2.so
 ```
@@ -37,7 +37,7 @@ Grab the Java Development Kit (JDK) as `.tar.gz` from the [Oracle Download Page]
 
 Extract JDK and move it to /opt:
 
-```
+``` bash
 cd ~/Downloads
 tar xf jdk-8u121-linux-x64.tar.gz
 sudo mv jdk1.8.0_121 /opt/
@@ -46,7 +46,7 @@ sudo ln -svf /opt/jdk1.8.0_121/bin/java /usr/bin/java
 
 To enable Java in Firefox:
 
-```
+``` bash
 mkdir -p ~/.mozilla/plugins
 ln -s /opt/jdk1.8.0_121/jre/lib/amd64/libnpjp2.so ~/.mozilla/plugins/libnpjp2.so
 ```