Minor updates to readme (#233)

README.md

@@ -29,7 +29,8 @@ your devices. Every new device you sign into will have access to these tokens.
 ### Offline Mode
 
 ente generates 2FA tokens offline, so your network connectivity will not get in
-the way of your workflow.
+the way of your workflow. If you wish to use the app without an account for e2ee
+backups, you can do that as well.
 
 ### Import and Export Tokens
 
@@ -41,7 +42,10 @@ You can add tokens to ente by one of the following methods:
     otpauth://totp/provider.com:you@email.com?secret=YOUR_SECRET
     ```
 
-You can export the codes you have added to ente, to either an **encrypted** or plain text file. 
+You can export the codes you have added to ente, to either an **encrypted** or
+plain text file. The encrypted backups can be accessed through the app, as well
+as a standalone CLI tool. [Read
+more](migration-guides/encrypted_export.md#how-to-use-the-exported-data).
 
 
 ## 📲 Download

migration-guides/encrypted_export.md

@@ -51,13 +51,13 @@ This section contains the parameters that were using during KDF operation:
 As mentioned above, the auth data is encrypted using a key that's derived by using user provided password & kdf params.
 For encryption, we are using `XChaCha20-Poly1305` algorithm.
 
-## How to use the export data
+## How to use the exported data
 
 * **ente Authenticator app**: You can directly import the codes in the ente Authenticator app.
   > Settings -> Data -> Import Codes -> ente Encrypted export.
 
-* **Decryption Tool** : You can download the [decrypt tool](decrypt/decrypt) and run the following command.
+* **Decryption Tool** : You can download the prebuilt [decryption tool](decrypt/decrypt) (or build it from [source](decrypt)) and run the following command.
          
-  ```./decrypt <export_file> <password> <output_file>```
-         
-
+```
+  ./decrypt <export_file> <password> <output_file>
+```