Say in the README's opening that the backup writes keywords

The opening said the backup keeps Ente's ML data for each file but did
not say it leaves out the CLIP embedding and writes the file's keywords
in its place. That now has a sentence of its own, and the rest of the
long sentence is split into shorter ones.

Model: opus-5-5

README.md

@@ -10,12 +10,13 @@ account into a deduplicated local directory tree, skipping files that already
 exist on disk and continuing past individual download failures instead of
 crashing. For each file it persists the basic metadata fields quak keeps (title,
 file type, creation and modification time, latitude, longitude, content hash),
-its update time, the private and public magic metadata in full, Ente's ML data
-for it when there is any, and, for an image (for a live photo, its image), its
-original's EXIF and XMP, with its dimensions for a JPEG only; for a video it
-keeps none of these three. It runs unattended from cron (see "Running the backup
-from cron"). A helper subcommand can detect and regenerate missing thumbnails,
-encrypting and uploading them back to the server.
+its update time, and the private and public magic metadata in full. It keeps any
+ML data Ente has for the file, except the CLIP embedding, and writes the file's
+keywords in place of the embedding. For an image (for a live photo, its image),
+it keeps its original's EXIF and XMP, with its dimensions for a JPEG only. For a
+video it keeps none of these three. It runs unattended from cron (see "Running
+the backup from cron"). A helper subcommand can detect and regenerate missing
+thumbnails, encrypting and uploading them back to the server.
 
 ## Getting Started