Merge pull request #32 from rasatpc/why-fvwm

I am just going to merge and fix the issues caught by @ThomasAdam , and do some small edits myself.

@rasatpc, It would really help us out if you learned git a bit better, no need to open multiple pull requests for the same thing. Yes it is new and different, but once you learn it it will make both your contributions and our reviews easier.

Wiki/NewToFvwm/WhyFvwm/index.md

@@ -10,27 +10,35 @@ Fvwm is a very old project and at one time was a fairly
 popular window manager, and is now a tiny project still used
 by lots of core users. What is it about fvwm that users like?
 
-+ Fvwm is light weight and fast. Fvwm is built on top of X11,
+{% capture fvwmtxt %}
+<p><strong>Fvwm is light weight and fast.</strong> - Fvwm is built on top of X11,
   and doesn't use a lot of additional libraries or widget
   sets, as such it has a very small foot print on top of
-  the already running X server, making it quite sleek.
+  the already running X server, making it quite sleek.</p>
 
-+ Fvwm is very stable, and preforms its task as a window manager
-  very well. It is very rare fvwm crashes, and most instability
-  is the application itself.
+<p><strong>Fvwm is very stable and performs its task as a window manager
+  very well.</strong> - It is very rare fvwm crashes, and most instability
+  is the application itself.</p>
 
-+ Fvwm is extremely configurable, and you can customize almost
-  every possible aspect of your desktop. Though this does take
+<p><strong>Fvwm is extremely configurable.</strong> - You can customize almost
+  every possible aspect of your desktop. However, this does take
   a lot of work to both learn how to configure fvwm and how
-  to put your dream configuration into practice.
+  to put your dream configuration into practice.</p>
+{% endcapture %}
+{% include fvwmwindow.html
+title="FVWM"
+color="no color"
+content=fvwmtxt %}
+
+## Fvwm features and capabilities:
 
 + Fvwm has the retro Motif look, similar to CDE. But fvwm doesn't
   need to look retro, and can be configured to have modern sleek
   looks, to fantasy looks. Did I mention fvwm is extremely
   configurable?
 
 + Fvwm has a wide range of modules that can be used to improve
-  the experience. These include a pager which shows all the
+  the experience. These include a pager that shows all the
   virtual pages and desktops. And modules to build panels,
   and even interactive forums. Even more configurability.
 
@@ -45,15 +53,19 @@ by lots of core users. What is it about fvwm that users like?
   while using modern software, and fvwm-crystal, which gives a
   nice sleek look.
 
-Fvwm is quite versatile, but in order to get the most out of
+**Fvwm is versatile**, but in order to get the most out of
 fvwm, you need to be willing to take the time to learn its
 command syntax (which is just the configuration file syntax).
 As you learn how to tell fvwm how to handle your windows,
 you can tweak fvwm into your own dream window manager. Okay,
 there are limits as to what fvwm can do, but within its
 structure, there is a lot of power.
 
-# What are fvwm's weaknesses?
+<em><strong>I like fvwm’s approach</strong> - no defaults and everything is
+up to the user. I can hardly imagine myself using anything else.
+Even with my lame coding style, fvwm meets my needs perfectly.</em>
+
+## What are fvwm's weaknesses?
 
 If fvwm was so great, why isn't everyone using it? And though I
 agree with that, the reality is fvwm requires a lot of effort
@@ -66,17 +78,17 @@ be used as a starting point, such as the [DefaultConfig](
 {{ "/DefaultConfig" | prepend: site.wikiurl }}). But making
 changes to fvwm still requires reading through the config file and
 understanding what to change. There are no GUI tools for this
-(partly because an GUI tool couldn't reasonable hold all the
+(partly because a GUI tool couldn't reasonably hold all the
 options fvwm has) and learning what to change can take a little
 bit of trial and error.
 
-Fvwm's isn't built using any modern widget set or frame work, and
+Fvwm's isn't built using any modern widget set or framework, and
 though its modules can allow some building of interactive UI elements,
 they are a bit primitive and don't contain a lot of modern features.
-Though you can build tools using modern frame works that talk to
+Though you can build tools using modern frameworks that talk to
 fvwm.
 
-Fvwm isn't for everyone, but if a quick, fast, low memory use, and
+Fvwm isn't for everyone, but if a quick, fast, low-memory use and
 very customizable window manager sounds good to you, give it a try.
 I would start by using the [DefaultConfig](
 {{ "/DefaultConfig" | prepend: site.wikiurl }}),