diff options
| author | Hans Bolinder <hasse@erlang.org> | 2015-10-13 14:02:48 +0200 |
|---|---|---|
| committer | Hans Bolinder <hasse@erlang.org> | 2015-12-09 13:05:34 +0100 |
| commit | 3e0e79218065458b816cd726bd637f1ecd00a882 (patch) | |
| tree | 72b89dc87ae86251adfd9d504d2518e4614101cd /lib/observer/doc/src/ttb_ug.xml | |
| parent | 646e1b9e6a836526865f15582bb22c600c54d26a (diff) | |
| download | erlang-3e0e79218065458b816cd726bd637f1ecd00a882.tar.gz | |
[observer] Correct documentation
Fix mistakes found by 'xmllint'.
Diffstat (limited to 'lib/observer/doc/src/ttb_ug.xml')
| -rw-r--r-- | lib/observer/doc/src/ttb_ug.xml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/lib/observer/doc/src/ttb_ug.xml b/lib/observer/doc/src/ttb_ug.xml index ba8c997133..e2a28d67d0 100644 --- a/lib/observer/doc/src/ttb_ug.xml +++ b/lib/observer/doc/src/ttb_ug.xml @@ -320,7 +320,7 @@ do_print(Out,{trace_ts,P,return_from,{M,F,A},R,Ts},N) -> </code> </section> <section> - <label>Overload protection</label> + <title>Overload protection</title> <p>When tracing live systems, special care needs to be always taken not to overload a node with too heavy tracing. <c>ttb</c> provides the <c>overload</c> option to help to address the problem.</p> @@ -747,7 +747,7 @@ f3() -> of the <c>ttb</c> for setting trace flags on processes and trace patterns for call trace, i.e. the functions <c>p</c>, <c>tp</c>, <c>tpl</c>, <c>ctp</c>, <c>ctpl</c> and <c>ctpg</c>. There are only - two things added by <c>ttb</c> for these functions: + two things added by <c>ttb</c> for these functions:</p> <list type="bulleted"> <item>all calls are stored in the history buffer and can be recalled and stored in a configuration file. This makes it @@ -756,9 +756,8 @@ f3() -> typing when using <c>ttb</c> from the erlang shell;</item> <item>shortcuts are provided for the most common match specifications (in order not to force the user to use - <c>dbg:fun2ms</c> continually</item>). + <c>dbg:fun2ms</c> continually).</item> </list> - </p> <p>Use <c>list_history/0</c> to see the content of the history buffer, and <c>run_history/1</c> to re-execute one of the entries. </p> |