From: drh <drh@noemail.net>
Date: Thu, 28 Mar 2019 01:00:37 +0000 (+0000)
Subject: Improvements to the README.md file.  No code changes.
X-Git-Tag: version-3.28.0~83
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=40f827a65e3328b072a37eb14dcf93cccfd5aba3;p=thirdparty%2Fsqlite.git

Improvements to the README.md file.  No code changes.

FossilOrigin-Name: bbdbaf84a52937ccf877072a8b01b07f7b9c037c59ba54df72ca888d5404cbad
---

diff --git a/README.md b/README.md
index 6dddf8f399..4fdbb868a3 100644
--- a/README.md
+++ b/README.md
@@ -41,7 +41,7 @@ archives or [SQLite archives](https://sqlite.org/cli.html#sqlar) as follows:
      [SQLite-archive](https://www.sqlite.org/src/sqlar/sqlite.sqlar?r=release).
 
   *  For other check-ins, substitute an appropriate branch name or
-     tag or hash prefix for "release" in the URLs of the previous
+     tag or hash prefix in place of "release" in the URLs of the previous
      bullet.  Or browse the [timeline](https://www.sqlite.org/src/timeline)
      to locate the check-in desired, click on its information page link,
      then click on the "Tarball" or "ZIP Archive" links on the information
@@ -313,18 +313,19 @@ If you obtained an SQLite source tree from a secondary source, such as a
 GitHub mirror, and you want to verify that it has not been altered, there
 are a couple of ways to do that.
 
-If you have an official release version of SQLite, and you are using the
+If you have a release version of SQLite, and you are using the
 `sqlite3.c` amalgamation, then SHA3-256 hashes for the amalgamation are
 available in the [change log](https://www.sqlite.org/changes.html) on
 the official website.  After building the `sqlite3.c` file, you can check
-that is authentic by comparing the hash.  This does not ensure that the
+that it is authentic by comparing the hash.  This does not ensure that the
 test scripts are unaltered, but it does validate the deliverable part of
-the code and only involves computing and comparing a single hash.
+the code and the verification process only involves computing and
+comparing a single hash.
 
 For versions other than an official release, or if you are building the
 `sqlite3.c` amalgamation using non-standard build options, the verification
 process is a little more involved.  The `manifest` file at the root directory
-of the source tree ([example](https://sqlite.org/src/artifact/bd49a8271d650fa8))
+of the source tree
 contains either a SHA3-256 hash (for newer files) or a SHA1 hash (for 
 older files) for every source file in the repository.  You can write a script
 to extracts hashes from `manifest` and verifies the hashes against the 
@@ -334,9 +335,13 @@ have.  The `manifest.uuid` file should contain the SHA3-256 hash of the
 `manifest` file.  If all of the above hash comparisons are correct, then
 you can be confident that your source tree is authentic and unadulterated.
 
+The format of the `manifest` file should be mostly self-explanatory, but
+if you want details, they are available
+[here](https://fossil-scm.org/fossil/doc/trunk/www/fileformat.wiki#manifest).
+
 ## Contacts
 
-The main SQLite webpage is [http://www.sqlite.org/](http://www.sqlite.org/)
+The main SQLite website is [http://www.sqlite.org/](http://www.sqlite.org/)
 with geographically distributed backups at
 [http://www2.sqlite.org/](http://www2.sqlite.org) and
 [http://www3.sqlite.org/](http://www3.sqlite.org).
diff --git a/manifest b/manifest
index 6d666442e9..54426c06d2 100644
--- a/manifest
+++ b/manifest
@@ -1,12 +1,12 @@
-C Support\sbuilding\sthe\sTcl\sbindings\sDLL\susing\sMSVC.
-D 2019-03-27T14:59:56.710
+C Improvements\sto\sthe\sREADME.md\sfile.\s\sNo\scode\schanges.
+D 2019-03-28T01:00:37.995
 F .fossil-settings/empty-dirs dbb81e8fc0401ac46a1491ab34a7f2c7c0452f2f06b54ebb845d024ca8283ef1
 F .fossil-settings/ignore-glob 35175cdfcf539b2318cb04a9901442804be81cd677d8b889fcc9149c21f239ea
 F LICENSE.md df5091916dbb40e6e9686186587125e1b2ff51f022cc334e886c19a0e9982724
 F Makefile.in 236d2739dc3e823c3c909bca2d6cef93009bafbefd7018a8f3281074ecb92954
 F Makefile.linux-gcc 7bc79876b875010e8c8f9502eb935ca92aa3c434
 F Makefile.msc fb6dc0c6b09e491b3ad87fed2e1c63ace1b474d4c01091157d63839d376e54c8
-F README.md ebcdb6d5656020ef5ca37a6fc1ad89b4c80560ea33a3d70c250f9b845cf9da62
+F README.md 623c225551b176659e443ae9e466e91a2c8ff16157260618295db91aef0800b7
 F VERSION 288d756b1b7be03ecdbf1795c23af2c8425f2e46ba6979a14ef53360308f080d
 F aclocal.m4 a5c22d164aff7ed549d53a90fa56d56955281f50
 F art/sqlite370.eps aa97a671332b432a54e1d74ff5e8775be34200c2
@@ -1813,8 +1813,7 @@ F vsixtest/vsixtest.tcl 6a9a6ab600c25a91a7acc6293828957a386a8a93
 F vsixtest/vsixtest.vcxproj.data 2ed517e100c66dc455b492e1a33350c1b20fbcdc
 F vsixtest/vsixtest.vcxproj.filters 37e51ffedcdb064aad6ff33b6148725226cd608e
 F vsixtest/vsixtest_TemporaryKey.pfx e5b1b036facdb453873e7084e1cae9102ccc67a0
-P 5be64ea8e33f632f9c337feac9b0663d8e6e59fc9a71e5d832d9fd905c06458e 8d0153996a3685a9b109a01fea0cba76e4296b010e96fc0db43fa6fde54d1965
-R 7c85fab2a8d644966400f11845d3ad11
-T +closed 8d0153996a3685a9b109a01fea0cba76e4296b010e96fc0db43fa6fde54d1965
-U mistachkin
-Z 5b4f719413f567097ebdba430d0cf7aa
+P b2011c13173114505705d2ff2ba6f476697d51aca0bddd585a9e5a639dca41e2
+R 125af71b8b5fa954757389f2105f8b01
+U drh
+Z e7286ca0ff41050ec1d4c73a21236495
diff --git a/manifest.uuid b/manifest.uuid
index 482b511afd..173beec6b9 100644
--- a/manifest.uuid
+++ b/manifest.uuid
@@ -1 +1 @@
-b2011c13173114505705d2ff2ba6f476697d51aca0bddd585a9e5a639dca41e2
\ No newline at end of file
+bbdbaf84a52937ccf877072a8b01b07f7b9c037c59ba54df72ca888d5404cbad
\ No newline at end of file