From: Christopher Howard <christopher.howard@qlfiles.net>
Date: Mon, 12 Feb 2018 18:55:40 +0000 (-0900)
Subject: Tests markup keywords
X-Git-Tag: v1.4.5~18^2~11^2~2
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=a501daa7dc6ad1a16aac46f68e75364734a239a3;p=librecmc%2Flibrecmc.git

Tests markup keywords
---

diff --git a/docs/System_Log.md b/docs/System_Log.md
index 52f1d81fb2..cf57e97a1e 100644
--- a/docs/System_Log.md
+++ b/docs/System_Log.md
@@ -17,7 +17,7 @@ output. Therefore, you will likely want to use the shell interface.
 
 Once logged in via SSH, use the `logread` command
 
-```
+```bash
 Usage: logread [options]
 Options:
     -s <path>		Path to ubus socket
@@ -37,7 +37,7 @@ Options:
 
 For example:
 
-```
+```bash
 root@libreCMC:~# logread | grep 'kern\.warn'
 Mon Jan 15 20:22:01 2018 kern.warn kernel: [    0.000000] No valid device tree found, continuing without
 Mon Jan 15 20:22:01 2018 kern.warn kernel: [    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
@@ -49,7 +49,7 @@ Mon Jan 15 20:22:01 2018 kern.warn kernel: [    0.752178] m25p80 spi0.0: found m
 One should be able to use `logread -e` instead of `grep`, but it seems
 that not all the same regular expressions work for both:
 
-```
+```bash
 root@libreCMC:~# logread -e 'kern\.warn' # and other similar variations
 (no output)
 ```