diff options
| author | Lukas Larsson <[email protected]> | 2016-07-01 17:32:51 +0200 |
|---|---|---|
| committer | Lukas Larsson <[email protected]> | 2016-07-13 14:54:56 +0200 |
| commit | 606e660f898264ea75680532c076c56bbe855633 (patch) | |
| tree | def63f8c7d35801d8927b9640c404f19f07a4a4c /erts/doc/src/time_correction.xml | |
| parent | 57c3246511434f42214e113b8902af10ab9cca49 (diff) | |
| download | otp-606e660f898264ea75680532c076c56bbe855633.tar.gz otp-606e660f898264ea75680532c076c56bbe855633.tar.bz2 otp-606e660f898264ea75680532c076c56bbe855633.zip | |
erts: Review of documentation changes
Diffstat (limited to 'erts/doc/src/time_correction.xml')
| -rw-r--r-- | erts/doc/src/time_correction.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/erts/doc/src/time_correction.xml b/erts/doc/src/time_correction.xml index dbaae4d852..8042ad3b99 100644 --- a/erts/doc/src/time_correction.xml +++ b/erts/doc/src/time_correction.xml @@ -247,7 +247,7 @@ everything that has anything to do with time. All timers, regardless of it is a <c>receive ... after</c> timer, BIF timer, or a timer in the - <seealso marker="stdlib:timer"><c>stdlib:timer</c></seealso> + <seealso marker="stdlib:timer"><c>stdlib:timer(3)</c></seealso> module, are triggered relative Erlang monotonic time. Even <seealso marker="#Erlang_System_Time">Erlang system time</seealso> is based on Erlang monotonic time. @@ -769,7 +769,7 @@ Take time stamps with <c>erlang:now/0</c> and calculate the difference in time with <seealso marker="stdlib:timer#now_diff/2"> - <c>timer:now_diff/2</c></seealso> in <c>STDLIB</c>. + <c>timer:now_diff/2</c></seealso>. </p> </dont> <do> @@ -915,7 +915,7 @@ EventTag = {Time, UMI}</code> <p>It can be required that your code must run on a variety of OTP installations of different OTP releases. If so, you cannot use the new API out of the box, as it will - not be available on old pre-OTP 18 releases. The solution + not be available on releases before OTP 18. The solution is <em>not</em> to avoid using the new API, as your code would then not benefit from the scalability and accuracy improvements made. Instead, use the |