Move guides in base directory to guides/ subdir

Move guides from the base directory into the guides/ sub directory to
provide better organisation of the documents on the website.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

content/enabling_new_hardware.md → content/guides/enabling_new_hardware.md

@@ -18,7 +18,7 @@ As Apertis aims to cater to a variety of use-cases and hardware
 platforms (with each platform providing its own balance of performance
 and features), developers are free to pick the hardware platform that
 provides the best match to their requirements. As an example, currently
-there are two big flavours of images:
+there are two big flavours of images targetted towards devices:
 
   - Target Images: The "default" images with a reference
     [HMI]( {{< ref "/glossary.md#hmi" >}} ) implementation. Expects hardware

content/scaleddownapertisimage.md → content/guides/scaleddownapertisimage.md

@@ -36,7 +36,7 @@ At this time the goal is were set out as:
 
 For Flash usage it's important to note that the intention is that the
 scaled down setup supports full system rollback. To cope with worst case
-of rollback, where the backup system and current systemdon't share any
+of rollback, where the backup system and current system don't share any
 data, it is required that one instance of the system fits in less then
 50% of the available flash space. In this particular case that means one
 instance of the system should not use more then 175 megabyte of flash
@@ -122,7 +122,7 @@ build.
 
 ## Step 1: Removal of unneeded data files
 
-Debian packages tend to come with batteries including, e.g. localisation
+Debian packages tend to come with batteries included, e.g. localisation
 for various languages, documentation (Readme files, man pages, info
 pages). While very useful on a most systems, on an headless embedded
 system those serve no purpose. Another big set of common data files for
@@ -144,7 +144,7 @@ revealed a 2 big candidates, the kernel and udev.
 First for the kernel, there are quite a few kernel modules in the
 standard Apertis images which provide drivers for all kinds of hardware.
 This is because Apartis kernel is a quite generic build with support for
-a wide range of hardware to easy development. However for a scaled down
+a wide range of hardware to ease development. However for a scaled down
 setup that hardware support isn't required, instead a far smaller kernel
 image can be used focussed on just supporting the required hardware. For
 the proof of concept images, the modules were simply removed in the same
@@ -191,14 +191,14 @@ flash footprint.
 
 ## Future work for footprint reduction and conclusions
 
-Analysing the curren image further it is clear that the footprint can be
+Analysing the current image further it is clear that the footprint can be
 reduced even further, the work thusfar has focussed on the biggest wins
 with the smallest impact on the overall Apertis sytem (allowing minimal
 images to be build with a small extra effort next to the normal set of
 images).
 
 There is clearly room for further pruning the set of package which get
-installed in the sytem by avoiding dependencies unless striclty
+installed in the system by avoiding dependencies unless striclty
 necessary, however in most cases that will require changes to the
 package build or the code. For example Cantebury depends on the
 pulseaudio libraries which shouldn't be required on a system with no