The README shows how a connected drive looks in Memona

Screenshots of the connection form, a connection with a wrong token, a
drive's PAGE.md and a save that met a change from elsewhere, taken in
Memona running this plugin against a live drive. They link to main so
they also render on the plugin page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -23,18 +23,14 @@ copy it; aindrive shows it only once.
 
 ![The connection form](https://git.capsulizers.com/commons/memona-plugin-aindrive/raw/branch/main/images/connection-form.png)
 
-Saving the connection checks the address and the token. With a wrong token the
-connection shows as **Disconnected**:
+Saving the connection checks the address and the token. It does not need the
+machine that shares the drive to be online, but its files only answer while
+that machine runs aindrive; until then they report the folder unavailable.
+
+With a wrong token the connection shows as **Disconnected**:
 
 ![A connected drive and one with a wrong token](https://git.capsulizers.com/commons/memona-plugin-aindrive/raw/branch/main/images/connections.png)
 
-The check does not need the machine that shares the drive to be online, but its
-files only answer while that machine runs aindrive. Until then the connection
-stays **Connected** and the plugin reports the drive unavailable, which Memona
-shows as a folder that cannot be read:
-
-![The drive's folder while its machine is offline](https://git.capsulizers.com/commons/memona-plugin-aindrive/raw/branch/main/images/offline-folder.png)
-
 ## What works
 
 Browsing folders, and reading, saving and deleting files. A token generated

manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 2,
-  "id": "jopilgue/aindrive",
+  "id": "memona/aindrive",
   "name": "aindrive",
   "version": "0.1.0",
   "apiVersion": "0.1.0",