aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2016-06-19 20:53:31 +1200
committerTom Ryder <tom@sanctum.geek.nz>2016-06-19 20:53:57 +1200
commitc7197dbf5a04a67518c08cc418fdfe8d62e05f4a (patch)
tree6ce7cd556bdd119ddf3e2b750edc83da1e4fe046
parentStrip trailing newlines (diff)
downloaddoomsh-c7197dbf5a04a67518c08cc418fdfe8d62e05f4a.tar.gz
doomsh-c7197dbf5a04a67518c08cc418fdfe8d62e05f4a.zip
Formatting
-rw-r--r--README.markdown8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.markdown b/README.markdown
index 2d3fb07..2edfe96 100644
--- a/README.markdown
+++ b/README.markdown
@@ -1,16 +1,16 @@
doomsh
======
-Use ulimit to severely restrict your Bash shell's resources, and see how long
+Use `ulimit` to severely restrict your Bash shell's resources, and see how long
you can last before segfaulting or giving up.
Not really important or useful in any way, but kind of fun to see what breaks
when resources are really tight, especially when it exposes problems in
-programs like failing to check for NULL returns from malloc(3).
+programs like failing to check for NULL returns from `malloc(3)`.
-On the author's machine, at level 5, even ls(1) doesn't work, let alone Vim.
+On the author's machine, at level 5, even `ls(1)` doesn't work, let alone Vim.
-If you're really crazy, you'll try and launch X processes from it, and watch
+If you're really crazy, you'll try and launch X11 processes from it, and watch
them twitch as they die.
READ THE LICENSE. THE AUTHOR WAIVES ALL RESPONSIBILITY FOR ANYTHING THIS DOES