aboutsummaryrefslogtreecommitdiffstats
path: root/lib/tools/doc/src/lcnt.xml
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2017-05-17 07:10:38 +0200
committerBjörn Gustavsson <[email protected]>2017-05-17 07:12:53 +0200
commit836d9bacfbea741d53e8f007c6a5e0ad37e7bd34 (patch)
treeac07d3769ade4d70ce3881094efc2e55ed7ccf64 /lib/tools/doc/src/lcnt.xml
parenta29bb639a5a0acf7da4d4fa65e4dd7c9cdcadb3c (diff)
downloadotp-836d9bacfbea741d53e8f007c6a5e0ad37e7bd34.tar.gz
otp-836d9bacfbea741d53e8f007c6a5e0ad37e7bd34.tar.bz2
otp-836d9bacfbea741d53e8f007c6a5e0ad37e7bd34.zip
Fix a few minor issues in the lcnt documentation
We generally avoid abbreviations such as "e.g." and "i.e." in the documentation. We write "Erlang", not "erlang" (except when referring to the erlang module).
Diffstat (limited to 'lib/tools/doc/src/lcnt.xml')
-rw-r--r--lib/tools/doc/src/lcnt.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/tools/doc/src/lcnt.xml b/lib/tools/doc/src/lcnt.xml
index 9c8ce148e9..6e66a957ab 100644
--- a/lib/tools/doc/src/lcnt.xml
+++ b/lib/tools/doc/src/lcnt.xml
@@ -38,7 +38,7 @@
<modulesummary>A runtime system Lock Profiling tool.</modulesummary>
<description>
<p>The <c>lcnt</c> module is used to profile the internal ethread locks in the
- Erlang Runtime System. With <c>lcnt</c> enabled, Internal counters in the
+ Erlang Runtime System. With <c>lcnt</c> enabled, internal counters in the
runtime system are updated each time a lock is taken. The counters stores
information about the number of acquisition tries and the number of collisions
that has occurred during the acquisition tries. The counters also record the
@@ -47,17 +47,17 @@
<p>
The data produced by the lock counters will give an estimate on how well
the runtime system will behave from a parallelizable view point for the
- scenarios tested. This tool was mainly developed to help erlang runtime
+ scenarios tested. This tool was mainly developed to help Erlang runtime
developers iron out potential and generic bottlenecks.
</p>
<p>Locks in the emulator are named after what type of resource they protect and where
in the emulator they are initialized, those are lock 'classes'. Most of those
locks are also instantiated several times, and given unique identifiers, to increase
locking granularity. Typically an instantiated lock protects a disjunct set of
- the resource, i.e ets-tables, processes or ports. In other cases it protects a
- specific range of a resource, e.g. <c>pix_lock</c> which protects index to process
+ the resource, for example ets tables, processes or ports. In other cases it protects a
+ specific range of a resource, for example <c>pix_lock</c> which protects index to process
mappings, and is given a unique number within the class. A unique lock in <c>lcnt</c>
- is referenced by a name (class) and an identifier, <c>{Name, Id}</c>.
+ is referenced by a name (class) and an identifier: <c>{Name, Id}</c>.
</p>
<p>Some locks in the system are static and protects global resources, for example
<c>bif_timers</c> and the <c>run_queue</c> locks. Other locks are dynamic and not