commit 37d108a5abb9e81fde6f1f47169d1130294d08e0
Author:     Simon Howard <fraggle+github@gmail.com>
AuthorDate: Sat Nov 26 21:35:08 2016 -0500
Commit:     GitHub <noreply@github.com>
CommitDate: Sat Nov 26 21:35:08 2016 -0500

    PHILOSOPHY: Minor formatting fixes
---
 PHILOSOPHY.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/PHILOSOPHY.md b/PHILOSOPHY.md
index bbcce464..5f309b03 100644
--- a/PHILOSOPHY.md
+++ b/PHILOSOPHY.md
@@ -49,7 +49,7 @@ different ways. Examples are:
    Chocolate Doom as a faithful substitute.
  * Demo compatibility: Doom was one of the first games to develop a
    ‘speedrunning’ community, and thousands of recordings of Doom
-   gameplay (.lmp demo files) exist in the Compet-N archive. Chocolate
+   gameplay (`.lmp` demo files) exist in the Compet-N archive. Chocolate
    Doom aims for the highest standard of demo compatibility with
    Vanilla Doom, a goal that is often complicated by obscure behavior
    that can be difficult to reproduce.
@@ -70,7 +70,7 @@ These are considered part of the Vanilla experience and ought to be
 treated as such. Some examples are:

  * The novert setting, which reproduces the functionality of
-   novert.exe.
+   `novert.exe`.
  * The `-deh` parameter, which loads Dehacked patches like dehacked.exe
    does under DOS. Chocolate Doom imposes the same limitations that
    Vanilla Dehacked does.
@@ -100,8 +100,8 @@ situations where changes are considered acceptable:
  3. Supporting obsolete technology is not a goal: it’s considered
     acceptable that Chocolate Doom does not support every type of
     hardware from 1993. However, Chocolate Doom should aim to recreate
-    the functionality in a modern way. Examples of technology that
-    isn’t supported are:
+    the functionality in a modern way. Examples of technologies that
+    aren’t supported are:

     - No support for IPX networks, but TCP/IP is supported instead.
     - No support for dial-up/serial connections; modern operating
@@ -114,9 +114,9 @@ situations where changes are considered acceptable:
     - There are new key bindings for actions that can’t be rebound with
       Vanilla Doom, because it’s useful for portability to machines
       that don’t have a full keyboard.
-    - There are additional mouse and joystick key bindings that let you
-      perform actions with them that can only be done with the keyboard
-      in Vanilla Doom.
+    - There are additional mouse and joystick button bindings that let
+      you perform actions with them that can only be done with the
+      keyboard in Vanilla Doom.
     - Chocolate Doom includes some hacks to support the Doom 3: BFG
       Edition IWAD files. The assumption is that being able to at least
       play is better than nothing, even if it’s not Vanilla behavior.