aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLuke Imhoff <[email protected]>2019-03-14 07:19:29 -0500
committerGitHub <[email protected]>2019-03-14 07:19:29 -0500
commitae6ac777fe55b5aec05a167109efc555cdcd3465 (patch)
tree7f227e3819689f174cca899e15fb92f61a568179
parent620ac3e68c5bc8b36143965fcf2892a07dc005c4 (diff)
downloadotp-ae6ac777fe55b5aec05a167109efc555cdcd3465.tar.gz
otp-ae6ac777fe55b5aec05a167109efc555cdcd3465.tar.bz2
otp-ae6ac777fe55b5aec05a167109efc555cdcd3465.zip
retranspissions -> retransmissions
-rw-r--r--erts/doc/src/alt_dist.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/erts/doc/src/alt_dist.xml b/erts/doc/src/alt_dist.xml
index e6245130fc..7c997cae20 100644
--- a/erts/doc/src/alt_dist.xml
+++ b/erts/doc/src/alt_dist.xml
@@ -60,7 +60,7 @@
parts of the logic in Erlang code, and you perhaps do not
even need a new driver for the protocol. One example could
be Erlang distribution over UDP using <c>gen_udp</c> (your
- Erlang code will of course have to take care of retranspissions,
+ Erlang code will of course have to take care of retransmissions,
etc in this example). That is, depending on what you want
to do you perhaps do not need to implement a driver at all
and can then skip the driver related sections below.