Help cleanup

Large list of changes, including formatting and typos for most commands.

More substantive changes have been made to alias, bind, block, break,
builtin, case, cd, commandline, count, else, emit, fish_config, funced,
function, functions, history, math, mimedb, nextd, not, popd, prevd,
pushd, pwd, random, read, set, set_color, switch, test, trap, type,
ulimit, umask, and while.

1 files changed, 30 insertions, 31 deletions

diff --git a/doc_src/ulimit.txt b/doc_src/ulimit.txt
index 6e21eba3..7b4e3c45 100644
--- a/doc_src/ulimit.txt
+++ b/doc_src/ulimit.txt
@@ -1,67 +1,66 @@
-\section ulimit ulimit - set or get the shells resource usage limits
+\section ulimit ulimit - set or get resource usage limits
 
 \subsection ulimit-synopsis Synopsis
 <tt>ulimit [OPTIONS] [LIMIT]</tt>
 
 \subsection ulimit-description Description
 
-The ulimit builtin is used to set the resource usage limits of the
-shell and any processes spawned by it.  If a new limit value is
-omitted, the current value of the limit of the resource is printed.
+\c ulimit builtin sets or outputs the resource usage limits of the
+shell and any processes spawned by it. If a new limit value is
+omitted, the current value of the limit of the resource is printed; otherwise,
+the specified limit is set to the new value.
 
 Use one of the following switches to specify which resource limit to set or report:
 
-- <code>-c</code> or <code>--core-size</code> The maximum size of core files created. By setting this limit to zero, core dumps can be disabled.
-- <code>-d</code> or <code>--data-size</code> The maximum size of a process's data segment
-- <code>-f</code> or <code>--file-size</code> The maximum size of files created by the shell
-- <code>-l</code> or <code>--lock-size</code> The maximum size that may be locked into memory
-- <code>-m</code> or <code>--resident-set-size</code> The maximum resident set size
-- <code>-n</code> or <code>--file-descriptor-count</code> The maximum number of open file descriptors (most systems do not allow this value to be set)
-- <code>-s</code> or <code>--stack-size</code> The maximum stack size
-- <code>-t</code> or <code>--cpu-time</code> The maximum amount of cpu time in seconds
-- <code>-u</code> or <code>--process-count</code> The maximum number of processes available to a single user
-- <code>-v</code> or <code>--virtual-memory-size</code> The maximum amount of virtual memory available to the shell. If supported by OS.
+- <code>-c</code> or <code>--core-size</code>: the maximum size of core files created. By setting this limit to zero, core dumps can be disabled.
+- <code>-d</code> or <code>--data-size</code>: the maximum size of a process' data segment.
+- <code>-f</code> or <code>--file-size</code>: the maximum size of files created by the shell.
+- <code>-l</code> or <code>--lock-size</code>: the maximum size that may be locked into memory.
+- <code>-m</code> or <code>--resident-set-size</code>: the maximum resident set size.
+- <code>-n</code> or <code>--file-descriptor-count</code>: the maximum number of open file descriptors (most systems do not allow this value to be set).
+- <code>-s</code> or <code>--stack-size</code>: the maximum stack size.
+- <code>-t</code> or <code>--cpu-time</code>: the maximum amount of CPU time in seconds.
+- <code>-u</code> or <code>--process-count</code>: the maximum number of processes available to a single user.
+- <code>-v</code> or <code>--virtual-memory-size</code> The maximum amount of virtual memory available to the shell.
 
 Note that not all these limits are available in all operating systems.
 
 The value of limit can be a number in the unit specified for
-the resource or one of the special values hard, soft, or unlimited,
+the resource or one of the special values <tt>hard</tt>, <tt>soft</tt>, or <tt>unlimited</tt>,
 which stand for the current hard limit, the current soft limit, and no
 limit, respectively.
 
 If limit is given, it is the new value of the specified resource. If
-no option is given, then -f is assumed. Values are in kilobytes,
-except for -t, which is in seconds and -n and -u, which are unscaled
+no option is given, then \c -f is assumed. Values are in kilobytes,
+except for \c -t, which is in seconds and \c -n and \c -u, which are unscaled
 values. The return status is 0 unless an invalid option or argument is
 supplied, or an error occurs while setting a new limit.
 
-ulimit also accepts the following switches that determine what type of
+\c ulimit also accepts the following switches that determine what type of
 limit to set:
 
-- <code>-H</code> or <code>--hard</code> Set hard resource limit
-- <code>-S</code> or <code>--soft</code> Set soft resource limit
+- <code>-H</code> or <code>--hard</code> sets hard resource limit
+- <code>-S</code> or <code>--soft</code> sets soft resource limit
 
-A hard limit can only be decreased, once it is set it can not be
+A hard limit can only be decreased. Once it is set it cannot be
 increased; a soft limit may be increased up to the value of the hard
 limit. If neither -H nor -S is specified, both the soft and hard
 limits are updated when assigning a new limit value, and the soft
 limit is used when reporting the current value.
 
-The following additional options are also understood by ulimit:
+The following additional options are also understood by <tt>ulimit</tt>:
 
-- <code>-a</code> or <code>--all</code> Print all current limits
-- <code>-h</code> or <code>--help</code> Display help and exit
+- <code>-a</code> or <code>--all</code> prints all current limits
+- <code>-h</code> or <code>--help</code> displays help and exits.
 
-The fish implementation of ulimit should behave identically to the
+The \c fish implementation of \c ulimit should behave identically to the
 implementation in bash, except for these differences:
 
-- Fish ulimit supports GNU-style long options for all switches
-- Fish ulimit does not support the -p option for getting the pipe size. The bash implementation consists of a compile-time check that empirically guesses this number by writing to a pipe and waiting for SIGPIPE. Fish does not do this because it this method of determining pipe size is unreliable. Depending on bash version, there may also be further additional limits to set in bash that do not exist in fish.
-- Fish ulimit does not support getting or setting multiple limits in one command, except reporting all values using the -a switch
+- Fish \c ulimit supports GNU-style long options for all switches
+- Fish \c ulimit does not support the \c -p option for getting the pipe size. The bash implementation consists of a compile-time check that empirically guesses this number by writing to a pipe and waiting for SIGPIPE. Fish does not do this because it this method of determining pipe size is unreliable. Depending on bash version, there may also be further additional limits to set in bash that do not exist in fish.
+- Fish \c ulimit does not support getting or setting multiple limits in one command, except reporting all values using the -a switch
 
 \subsection ulimit-example Example
 
-<tt>ulimit -Hs 64</tt>
-
-would set the hard stack size limit to 64 kB:
+<tt>ulimit -Hs 64</tt> sets the hard stack size limit to 64 kB.