[RFC17] comment encoding must be in base64 without padding

rfc/0017_transaction_comment_encryption.md

@@ -104,7 +104,7 @@ It is recommended to randomly generate a random number of extra bytes to obscure
 
 ## Encoding in transaction document
 
-Encrypted message in encoded in base 64 in transaction comment directly (DUBP protocol already accept all base 64 characters).
+Encrypted message in encoded in base 64 (without padding) in transaction comment directly (DUBP protocol already accept all base 64 characters).
 
 ## Maximum message length