CHANGELOG and docs

CHANGELOG.md

@@ -1,4 +1,7 @@
-## 7.3.3 (unreleased)
+## 7.4.0 (unreleased)
+## New features
+- [PR #1017](https://github.com/rqlite/rqlite/pull/1017): Support restoring from SQLite data files. Fixes [issue #1005](https://github.com/rqlite/rqlite/issues/1016).
+### Implementation changes and bug fixes
 - [PR #1015](https://github.com/rqlite/rqlite/pull/1015): go mod (dependencies) updates.
 
 ## 7.3.2 (March 1st 2022)

DOC/RESTORE_FROM_SQLITE.md

@@ -1,11 +1,11 @@
 # Restoring from a SQLite dump file
 
-rqlite supports loading a node directly from two sources:
+rqlite supports loading a node directly from two sources, either of which can be used to restore from an existing [node backup](https://github.com/rqlite/rqlite/blob/master/DOC/BACKUPS.md):
 - An actual SQLite database file. This is the fastest way to initialize a rqlite node from an existing SQLite database.
-- SQLite dump file. This is another convenient manner to initialize a system from an existing SQLite database, or to restore from an existing [node backup](https://github.com/rqlite/rqlite/blob/master/DOC/BACKUPS.md). But if your database is large, it can be slow.
+- SQLite dump file. This is another convenient manner to initialize a system from an existing SQLite database, or to restore from an . But if your database is large, it can be slow.
 
 ## Examples
-The following examples show a trivial database being generated by `sqlite3`, the SQLite file being backed up, converted to the corresponding list of SQL commands, and then loaded into a rqlite node listening on localhost.
+The following examples show a trivial database being generated by `sqlite3`, the SQLite file being backed up, converted to the corresponding list of SQL commands, and then loaded into a rqlite node listening on localhost using each form.
 
 ### HTTP
  _Be sure to set the Content-type header as shown in each case._