aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHenrik Nord <[email protected]>2015-10-27 12:54:31 +0100
committerHenrik Nord <[email protected]>2015-10-27 12:54:31 +0100
commit7dc9eefa341fbfae0ebc55a88b96a375c611e3a4 (patch)
tree07e4fb020fb49b44477971f1850c2b445d3b23c9
parentc2894ea0f79d9f27b0c3841fc77ad88aa7fd38ee (diff)
parent25a693d99c8d9220addf8d9955299feedb4ddb92 (diff)
downloadotp-7dc9eefa341fbfae0ebc55a88b96a375c611e3a4.tar.gz
otp-7dc9eefa341fbfae0ebc55a88b96a375c611e3a4.tar.bz2
otp-7dc9eefa341fbfae0ebc55a88b96a375c611e3a4.zip
Merge branch 'gomoripeti/bindoc_fix' into maint
* gomoripeti/bindoc_fix: Very minor fixes to binary handling documentation
-rw-r--r--system/doc/efficiency_guide/binaryhandling.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/system/doc/efficiency_guide/binaryhandling.xml b/system/doc/efficiency_guide/binaryhandling.xml
index 51f8c4ebf0..0964b759d8 100644
--- a/system/doc/efficiency_guide/binaryhandling.xml
+++ b/system/doc/efficiency_guide/binaryhandling.xml
@@ -190,15 +190,15 @@ Bin4 = <<Bin1/binary,17>>, %% 5 !!!
its size set to the size of the data stored in the binary, while
the binary object has extra space allocated.
The size of the binary object is either twice the
- size of <c>Bin0</c> or 256, whichever is larger. In this case
+ size of <c>Bin1</c> or 256, whichever is larger. In this case
it is 256.</item>
<item>Line 3 is more interesting.
<c>Bin1</c> <em>has</em> been used in an append operation,
- and it has 255 bytes of unused storage at the end, so the 3 new
+ and it has 252 bytes of unused storage at the end, so the 3 new
bytes are stored there.</item>
- <item>Line 4. The same applies here. There are 252 bytes left,
+ <item>Line 4. The same applies here. There are 249 bytes left,
so there is no problem storing another 3 bytes.</item>
<item>Line 5. Here, something <em>interesting</em> happens. Notice