diff --git a/bash4.markup b/bash4.markup
deleted file mode 100644
index 2e5690c..0000000
--- a/bash4.markup
+++ /dev/null
@@ -1,196 +0,0 @@
-====== Bash 4 - a rough overview ======
-
-:V4:
-
-Attention: Since Bash 4 has been around for quite some time now (4.3 will come soon), I consider it to be "standard". This page is not maintained anymore and is left here to keep your links working. See the [[scripting:bashchanges]] page for new stuff introduced.
-
-Besides many bugfixes since Bash 3.2, Bash 4 will bring some interesting new
-features for shell users and scripters. See also [[scripting:bashchanges]] for a small general overview with more details.
-
-Not all of the changes and news are included here, just the biggest or
-most interesting ones. The changes to completion, and the readline component
-are not covered. **Though, if you're familiar with these parts of Bash (and Bash 4),
-feel free to write a chapter here.**
-
-The complete list of fixes and changes is in the CHANGES or NEWS file of your
-Bash 4 distribution.
-
-
-The current available **stable** version is 4.4.18 release (February 03, 2018):
- * ftp://ftp.cwru.edu/pub/bash/bash-4.4.18.tar.gz
- * ftp://ftp.gnu.org/pub/gnu/bash/bash-4.4.18.tar.gz
-
-
-
-
-===== New or changed commands and keywords =====
-
-==== The new "coproc" keyword ====
-
-Bash 4 introduces the concepts of coprocesses, a well known feature of other
-shells. The basic concept is simple: It will start any command in the background
-and set up an array that is populated with accessible files that represent the
-filedescriptors of the started process.
-
-In other words: It lets you start a process in background and communicate with
-its input and output data streams.
-
-See [[syntax:keywords:coproc | The coproc keyword]]
-
-==== The new "mapfile" builtin ====
-
-The ''mapfile'' builtin is able to map the lines of a file directly into an
-array. This avoids having to fill an array yourself using a loop. It enables you to define
-the range of lines to read, and optionally call a callback, for example to
-display a progress bar.
-
-See: [[commands:builtin:mapfile]]
-
-==== Changes to the "case" keyword ====
-
-The ''case'' construct understands two new action list terminators:
-
-The '';&'' terminator causes execution to continue with the next action list
-(rather than terminate the ''case'' construct).
-
-The '';;&'' terminator causes the ''case'' construct to test the next given
-pattern instead of terminating the whole execution.
-
-See [[syntax:ccmd:case]]
-
-==== Changes to the "declare" builtin ====
-
-The ''-p'' option now prints all attributes and values of declared variables (or
-functions, when used with ''-f''). The output is fully re-usable as input.
-
-The new option ''-l'' declares a variable in a way that the content is
-converted to lowercase on assignment. For uppercase, the same applies to
-''-u''. The option ''-c'' causes the content to be capitalized before
-assignment.
-
-''declare -A'' declares associative arrays (see below).
-
-==== Changes to the "read" builtin ====
-
-The ''read'' builtin command has some interesting new features.
-
-The ''-t'' option to specify a timeout value has been slightly tuned. It now
-accepts fractional values and the special value 0 (zero). When ''-t 0'' is
-specified, ''read'' immediately returns with an exit status indicating if
-there's data waiting or not. However, when a timeout is given, and the ''read''
-builtin times out, any partial data recieved up to the timeout is stored in the
-given variable, rather than lost. When a timeout is hit, ''read'' exits with a
-code greater than 128.
-
-A new option, ''-i'', was introduced to be able to preload the input buffer with
-some text (when Readline is used, with ''-e''). The user is able to change the
-text, or press return to accept it.
-
-See [[commands:builtin:read]]
-
-==== Changes to the "help" builtin ====
-
-The builtin itself didn't change much, but the data displayed is more structured
-now. The help texts are in a better format, much easier to read.
-
-There are two new options: ''-d'' displays the summary of a help text, ''-m''
-displays a manpage-like format.
-
-==== Changes to the "ulimit" builtin ====
-
-Besides the use of the 512 bytes blocksize everywhere in POSIX mode, ''ulimit''
-supports two new limits: ''-b'' for max socket buffer size and ''-T'' for max
-number of threads.
-
-===== Expansions =====
-
-==== Brace Expansion ====
-
-The brace expansion was tuned to provide expansion results with leading zeros
-when requesting a row of numbers.
-
-See [[syntax:expansion:brace]]
-
-==== Parameter Expansion ===
-
-Methods to modify the case on expansion time have been added.
-
-On expansion time you can modify the syntax by adding operators to the parameter
-name.
-
-See [[syntax:pe#case_modification | Case modification on parameter expansion]]
-
-==== Substring expansion ====
-When using substring expansion on the positional parameters, a starting
-index of 0 now causes $0 to be prepended to the list (if the positional parameters are used). Before, this expansion
-started with $1:
-
-# this should display $0 on Bash v4, $1 on Bash v3
-echo ${@:0:1}
-
-
-==== Globbing ====
-
-There's a new shell option ''[[internals:shell_options#globstar | globstar]]''. When enabled, Bash will perform
-recursive globbing on ''**'' -- this means it matches all directories and files
-from the current position in the filesystem, rather than only the current level.
-
-The new shell option ''[[internals:shell_options#dirspell | dirspell]]'' enables spelling corrections on directory
-names during globbing.
-
-See [[syntax:expansion:globs]]
-
-===== Associative Arrays =====
-
-Besides the classic method of integer indexed arrays, Bash 4 supports associative arrays.
-
-An associative array is an array indexed by an arbitrary string, something like
-
-declare -A ASSOC
-
-ASSOC[First]="first element"
-ASSOC[Hello]="second element"
-ASSOC[Peter Pan]="A weird guy"
-
-
-See [[syntax:arrays]]
-
-===== Redirection =====
-
-There is a new ''&>>'' redirection operator, which appends the standard output
-and standard error to the named file. This is the same as the good old ''>>FILE 2>&1''
-notation.
-
-The parser now understands ''|&'' as a synonym for ''2>&1 |'', which redirects
-the standard error for a command through a pipe.
-
-See [[syntax:redirection]]
-
-===== Interesting new shell variables =====
-^Variable ^Description ^
-|[[syntax:shellvars#BASHPID|BASHPID]] | contains the PID of the current shell (this is different than what ''$$'' does!) |
-|[[syntax:shellvars#PROMPT_DIRTRIM|PROMPT_DIRTRIM]] | specifies the max. level of unshortened pathname elements in the prompt |
-|[[syntax:shellvars#FUNCNEST|FUNCNEST]] | control the maximum number of shell function recursions |
-
-See [[syntax:shellvars]]
-
-===== Interesting new Shell Options =====
-
-The mentioned shell options are **off by default** unless otherwise mentioned.
-
-^Option ^Description ^
-|''[[internals:shell_options#checkjobs | checkjobs]]'' | check for and report any running jobs at shell exit |
-|''[[internals:shell_options#compat31 | compat*]]'' | set compatiblity modes for older shell versions (influences regular expression matching in ''[[ ... ]]'' |
-|''[[internals:shell_options#dirspell | dirspell]]'' | enables spelling corrections on directory names during globbing |
-|''[[internals:shell_options#globstar | globstar]]'' | enables recursive globbing with ''**'' |
-|''[[internals:shell_options#lastpipe | lastpipe]]'' | (4.2) to execute the last command in a pipeline in the current environment |
-
-
-See [[internals:shell_options]]
-
-===== Misc =====
-
- * If a command is not found, the shell attempts to execute a shell function named ''command_not_found_handle'', supplying the command words as the function arguments. This can be used to display userfriendly messages or perform different command searches
- * The behaviour of the ''set -e'' (''errexit'') mode was changed, it now acts more intuitive (and is better documented in the manpage).
- * The output target for the ''xtrace'' (''set -x''/''set +x'') feature is configurable **since Bash 4.1** (previously, it was fixed to ''stderr''): a variable named [[syntax:shellvars#BASH_XTRACEFD|BASH_XTRACEFD]] can be set to the filedescriptor that should get the output
- * Bash 4.1 is able to log the history to syslog (only to be enabled at compile time in ''config-top.h'')
diff --git a/commands/builtin/caller.markup b/commands/builtin/caller.markup
deleted file mode 100644
index 3161a56..0000000
--- a/commands/builtin/caller.markup
+++ /dev/null
@@ -1,57 +0,0 @@
-====== The caller builtin command ======
-
-===== Synopsis =====
-caller [FRAMENUMBER]
-
-===== Description =====
-The ''caller'' builtin command is used to print execution frames of subroutine calls. Without giving a framenumber, the topmost execution frame information is printed ("who called me") wile linenumber and filename.
-
-When an execution frame number is given (0 - topmost), the linenumber, the subroutine (function) and the filename is printed. When an invalid execution frame number is given, it exists ''FALSE''. This way it can be used in a loop (see the examples section below).
-
-===== Examples =====
-
-==== Simple stack trace ====
-
-The code below defines a function ''die'' that is used to exit the program. It prints a list of execution frames, starting with the topmost frame (0). The topmost frame is the "caller of the die function", in this case function "f1".
-
-This way, you can print a "stack trace" for debugging or logging purposes.
-
-The code is made very simple, just to show the basic purposes.
-
-
-#!/bin/bash
-
-die() {
- local frame=0
- while caller $frame; do
- ((++frame));
- done
- echo "$*"
- exit 1
-}
-
-f1() { die "*** an error occured ***"; }
-f2() { f1; }
-f3() { f2; }
-
-f3
-
-
-**Output**
-
-12 f1 ./callertest.sh
-13 f2 ./callertest.sh
-14 f3 ./callertest.sh
-16 main ./callertest.sh
-*** an error occured ***
-
-
-===== Notes =====
- * ''caller'' produces no output unless used within a script that's run from a real file. It isn't particularly useful for interactive use, but can be used to create a decent ''die'' function to track down errors in moderately complex scripts. { bash /dev/stdin; } <<<$'f(){ g; }\ng(){ h; }\nh(){ while caller $((n++)); do :; done; }\nf'
- * For more sophisticated debugging, Bash extended debugging features are available and a number of special parameters that give more detail than caller (e.g. BASH_ARG{C,V}). Tools such as [[ http://bashdb.sourceforge.net/|Bashdb ]] can assist in using some of Bash's more advanced debug features.
- * The Bash manpage and help text specifies that the argument to ''caller'' is an "expr" (whatever that means). Only an integer is actually allowed, with no special interpretation of an "expression" as far as we can tell.
-
-===== Portability considerations =====
- * ''caller'' is not specified by POSIX(R)
- * the ''caller'' builtin command appeared in Bash version 3.0
-
diff --git a/commands/builtin/continuebreak.markup b/commands/builtin/continuebreak.markup
deleted file mode 100644
index 8eaf805..0000000
--- a/commands/builtin/continuebreak.markup
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-
-
-
-
You don't have an account yet? Just get one: Register