Skip to content

Commit 24a9b6f

Browse files
author
Hgh
committed
Updated encoding readme file
1 parent c01af8f commit 24a9b6f

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

encoding/README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ data which will be sent over an API response or special characters on a debug co
2121
other hand, to decode the encoded data you need the algorithm that was used to encode data plus the key of encryption.
2222

2323
But what is happening under the hood? In cryptography, every object will be converted to an array of bytes. This array
24-
will be used as the input of a process and the result of the process will be another array of bytes. The last array of bytes
25-
is our encoded data.
24+
will be used as the input of a process and the result of the process will be another array of bytes. The last array of
25+
bytes is our encoded data.
2626

2727
In action, we encounter two objects from different types as input and output. So the question is how we should convert
28-
things to an array of bytes. Or vice versa how we can encode the array of bytes to a human-readable string for
28+
things to an array of bytes. Or vice versa how we can decode the array of bytes to a human-readable string for
2929
debugging, storable value in a database or transmittable through a RESTful API response? You'll find the
3030
solution [Here](#sample).
3131

@@ -42,7 +42,8 @@ echo -n 'Hello, World' | od -vt x1
4242
Each represented byte in output is equal to the `Hello, World` correspondent character in ASCII Table. e.g. `H` is equal
4343
to `0x48` and so on. So every letter in the string is converted into a character of ASCII table. The `String` is a basic
4444
data type. The main question is what we should do if we'd like to represent complex data structures in an array of bytes
45-
and vice versa. It seems easy at first glance, it's not though. For that, it's highly recommended to persuade the next sections.
45+
and vice versa. It seems easy at first glance, it's not though. For that, it's highly recommended to persuade the next
46+
sections.
4647

4748
- [Binary to Text Encoding](https://github.com/KeyvanArj/cryptography-in-use/tree/main/encoding/binary-to-text): This
4849
method will be used as the primitive tool in binary and text data manipulation.

0 commit comments

Comments
 (0)