1 files changed, 4 insertions, 4 deletions
diff --git a/44.md b/44.md
index 8f781b8..8f27fed 100644
--- a/44.md
+++ b/44.md
@@ -63,7 +63,7 @@ NIP-44 version 2 has the following design characteristics:
 - SHA256 is used instead of SHA3 or BLAKE because it is already used in nostr. Also BLAKE's speed advantage
  is smaller in non-parallel environments.
 - A custom padding scheme is used instead of padmé because it provides better leakage reduction for small messages.
- Base64 encoding is used instead of another compression algorithm because it is widely available, and is already used in nostr.
+- Base64 encoding is used instead of another encoding algorithm because it is widely available, and is already used in nostr.
 ### Encryption
@@ -86,7 +86,7 @@ NIP-44 version 2 has the following design characteristics:
   - Content must be encoded from UTF-8 into byte array
   - Validate plaintext length. Minimum is 1 byte, maximum is 65535 bytes
   - Padding format is: `[plaintext_length: u16][plaintext][zero_bytes]`
-   - Padding algorithm is related to powers-of-two, with min padded msg size of 32
+   - Padding algorithm is related to powers-of-two, with min padded msg size of 32bytes
   - Plaintext length is encoded in big-endian as first 2 bytes of the padded blob
 5. Encrypt padded content
   - Use ChaCha20, with key and nonce from step 3
@@ -148,8 +148,8 @@ validation rules, refer to BIP-340.
  - `x[i:j]`, where `x` is a byte array and `i, j <= 0` returns a `(j - i)`-byte array with a copy of the
    `i`-th byte (inclusive) to the `j`-th byte (exclusive) of `x`.
 - Constants `c`:
-  - `min_plaintext_size` is 1. 1b msg is padded to 32b.
+  - `min_plaintext_size` is 1. 1bytes msg is padded to 32bytes.
-  - `max_plaintext_size` is 65535 (64kb - 1). It is padded to 65536.
+  - `max_plaintext_size` is 65535 (64kB - 1). It is padded to 65536bytes.
 - Functions
  - `base64_encode(string)` and `base64_decode(bytes)` are Base64 ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648), with padding)
  - `concat` refers to byte array concatenation

diff --git a/44.md b/44.md index 8f781b8..8f27fed 100644 --- a/44.md +++ b/44.md
@@ -63,7 +63,7 @@ NIP-44 version 2 has the following design characteristics:
63	- SHA256 is used instead of SHA3 or BLAKE because it is already used in nostr. Also BLAKE's speed advantage	63	- SHA256 is used instead of SHA3 or BLAKE because it is already used in nostr. Also BLAKE's speed advantage
64	is smaller in non-parallel environments.	64	is smaller in non-parallel environments.
65	- A custom padding scheme is used instead of padmé because it provides better leakage reduction for small messages.	65	- A custom padding scheme is used instead of padmé because it provides better leakage reduction for small messages.
66	- Base64 encoding is used instead of another compression algorithm because it is widely available, and is already used in nostr.	66	- Base64 encoding is used instead of another encoding algorithm because it is widely available, and is already used in nostr.
67		67
68	### Encryption	68	### Encryption
69		69
@@ -86,7 +86,7 @@ NIP-44 version 2 has the following design characteristics:
86	- Content must be encoded from UTF-8 into byte array	86	- Content must be encoded from UTF-8 into byte array
87	- Validate plaintext length. Minimum is 1 byte, maximum is 65535 bytes	87	- Validate plaintext length. Minimum is 1 byte, maximum is 65535 bytes
88	- Padding format is: `[plaintext_length: u16][plaintext][zero_bytes]`	88	- Padding format is: `[plaintext_length: u16][plaintext][zero_bytes]`
89	- Padding algorithm is related to powers-of-two, with min padded msg size of 32	89	- Padding algorithm is related to powers-of-two, with min padded msg size of 32bytes
90	- Plaintext length is encoded in big-endian as first 2 bytes of the padded blob	90	- Plaintext length is encoded in big-endian as first 2 bytes of the padded blob
91	5. Encrypt padded content	91	5. Encrypt padded content
92	- Use ChaCha20, with key and nonce from step 3	92	- Use ChaCha20, with key and nonce from step 3
@@ -148,8 +148,8 @@ validation rules, refer to BIP-340.
148	- `x[i:j]`, where `x` is a byte array and `i, j <= 0` returns a `(j - i)`-byte array with a copy of the	148	- `x[i:j]`, where `x` is a byte array and `i, j <= 0` returns a `(j - i)`-byte array with a copy of the
149	`i`-th byte (inclusive) to the `j`-th byte (exclusive) of `x`.	149	`i`-th byte (inclusive) to the `j`-th byte (exclusive) of `x`.
150	- Constants `c`:	150	- Constants `c`:
151	- `min_plaintext_size` is 1. 1b msg is padded to 32b.	151	- `min_plaintext_size` is 1. 1bytes msg is padded to 32bytes.
152	- `max_plaintext_size` is 65535 (64kb - 1). It is padded to 65536.	152	- `max_plaintext_size` is 65535 (64kB - 1). It is padded to 65536bytes.
153	- Functions	153	- Functions
154	- `base64_encode(string)` and `base64_decode(bytes)` are Base64 ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648), with padding)	154	- `base64_encode(string)` and `base64_decode(bytes)` are Base64 ([RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648), with padding)
155	- `concat` refers to byte array concatenation	155	- `concat` refers to byte array concatenation