docs(Bytes): use padding instead of endianness

Author: zhangyuannie

docs/bytes/Bytes.md

@@ -16,9 +16,9 @@
 
 The `Bytes` library has functions for working with bytes.
 
-#### Bytes, strings, numbers and endianness in Ethereum
+#### Bytes, strings, numbers and padding in Ethereum
 
-Ethereum uses the big endian format when working with strings/bytes, and little endian when working with other types (such as numbers and addresses). As an example, this is how we would store the string "abcd" in one full word (32 bytes):
+In Ethereum, strings and bytes are padded on the lower-order (right) side with zero-bytes, while other types (such as numbers and addresses) are padded on the higher-order side. As an example, this is how we would store the string "abcd" in one full word (32 bytes):
 
 `0x6162636400000000000000000000000000000000000000000000000000000000`
 
@@ -96,4 +96,4 @@ What is the value of `b` after this code has been run?
 
 The value will be `0`, but the internal representation would be `0x0000000000000000000000000000000000000000000000000000000000000054`, which lies outside of the allowed range so it is technically invalid.
 
-Finally, these sections deal with bytes in memory and on the stack. For bytes packed in storage, things can be different.
+Finally, these sections deal with bytes in memory and on the stack. For bytes packed in storage, things can be different.