Comment additions

Author: DaveCTurner

server/src/main/java/org/elasticsearch/repositories/blobstore/BlobStoreRepository.java

@@ -1835,7 +1835,7 @@ record RootBlobUpdateResult(RepositoryData oldRepositoryData, RepositoryData new
                         }));
                     }
 
-                    // Write the SnapshotInfo blob (we're already on a SNAPSHOT thread so no need to fork this)
+                    // Write the SnapshotInfo blob to the repo (we're already on a SNAPSHOT thread so no need to fork this)
                     assert ThreadPool.assertCurrentThreadPool(ThreadPool.Names.SNAPSHOT);
                     ActionListener.completeWith(allMetaListeners.acquire(), () -> {
                         SNAPSHOT_FORMAT.write(snapshotInfo, blobContainer(), snapshotId.getUUID(), compress);

server/src/main/java/org/elasticsearch/snapshots/SnapshotsService.java

@@ -1406,7 +1406,7 @@ private void finalizeSnapshotEntry(Snapshot snapshot, Metadata metadata, Reposit
     /**
      * Implements the finalization process for a snapshot: does some preparatory calculations, builds a {@link SnapshotInfo} and a
      * {@link FinalizeSnapshotContext}, calls {@link Repository#finalizeSnapshot} and handles the outcome by notifying waiting listeners
-     * and triggering the next snapshot-related activity.
+     * and triggering the next snapshot-related activity (another finalization, a batch of deletes, etc.)
      */
     // This only really makes sense to run against a BlobStoreRepository, and the division of work between this class and
     // BlobStoreRepository#finalizeSnapshot is kind of awkward and artificial; TODO consolidate all this stuff into one place and simplify