diff options
| author | Rickard Green <[email protected]> | 2013-01-29 01:59:53 +0100 |
|---|---|---|
| committer | Rickard Green <[email protected]> | 2013-01-29 01:59:53 +0100 |
| commit | cc469188a28ecbbef8e32415ffaa2c9e16bada5a (patch) | |
| tree | 0ac57b3703846805a6706cc9ba8b6b3f3d46e333 /erts/doc | |
| parent | 6bb1e114ef5dc0df8acb05a50fe3f7a1c5529a2c (diff) | |
| download | otp-cc469188a28ecbbef8e32415ffaa2c9e16bada5a.tar.gz otp-cc469188a28ecbbef8e32415ffaa2c9e16bada5a.tar.bz2 otp-cc469188a28ecbbef8e32415ffaa2c9e16bada5a.zip | |
Fix spelling in communication.xml
Thanks to Richard O'Keefe
Diffstat (limited to 'erts/doc')
| -rw-r--r-- | erts/doc/src/communication.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/erts/doc/src/communication.xml b/erts/doc/src/communication.xml index 6049123f6a..4025e41ef3 100644 --- a/erts/doc/src/communication.xml +++ b/erts/doc/src/communication.xml @@ -49,7 +49,7 @@ signals may be lost if the distribution channel goes down.</p> <p>The only signal ordering guarantee given is the following. If an entity sends multiple signals to the same destination entity, - the order will be preserved. That is, if <c>A</c> send + the order will be preserved. That is, if <c>A</c> sends a signal <c>S1</c> to <c>B</c>, and later sends the signal <c>S2</c> to <c>B</c>, <c>S1</c> is guaranteed not to arrive after <c>S2</c>.</p> @@ -69,7 +69,7 @@ <section> <title>Implementation</title> <p>The implementation of different asynchronous signals in the - VM may vary over time, but the behavior will always respect this + VM may vary over time, but the behaviour will always respect this concept of asynchronous signals being passed between entities as described above.</p> <p>By inspecting the implementation you might notice that some |