@@ -73,11 +73,11 @@
 </tr>
 
 <tr>
 <td>Import</td>
 <td>Import files and changesets</td>
-<td>File import ok. Changeset import currently on hold due to RL interference</td>
+<td>File import ok. Changeset import has restarted.</td>
 </tr>
 </table>
 </p>
 
 Passes to do:
@@ -96,11 +96,11 @@
 </li>
 <li> Generate a manifest file for a list of files (paths, ids), parent manifest references, user, timestamp, log message. Could be signed or not.
 </li>
 </ul>
 <br>
-With these actions (possible in combination) we can import the archive files first, needing only space for the revisions of a single file (bounded by the largest file in terms of size and history), with their delta-links mirroring the RCS structure. After that we can independently generate, import, and deltify the manifests for changesets. to finalize we simply 'rebuild' the repository. This should be fast without needing much temporary disk space either.
+With these actions (possibly in combination) we can import the archive files first, needing only space for the revisions of a single file (bounded by the largest file in terms of size and history), with their delta-links mirroring the RCS structure. After that we can independently generate, import, and deltify the manifests for changesets. To finalize we simply 'rebuild' the repository. This should be fast without needing much temporary disk space either.
 <br>
 Currently I am thinking about wanting a command
 <pre>
 fossil import-files SPECFILE
 </pre>