aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authordrh <drh@noemail.net>2010-08-31 15:38:51 +0000
committerdrh <drh@noemail.net>2010-08-31 15:38:51 +0000
commit3d3517ad3b229d60da33ed71f10ab6da3067d1b3 (patch)
treebee03d1b62d10c25af18be1a12d46757ce1f8ac7 /src
parent9f129f467e7961b3225a0ecc37d26cddc9155943 (diff)
downloadsqlite-3d3517ad3b229d60da33ed71f10ab6da3067d1b3.tar.gz
sqlite-3d3517ad3b229d60da33ed71f10ab6da3067d1b3.zip
Fix a documentation typo reported on the mailing list.
FossilOrigin-Name: c9fe0a2392ba4ae53d1dfcb986a67beeeb33519f
Diffstat (limited to 'src')
-rw-r--r--src/sqlite.h.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/sqlite.h.in b/src/sqlite.h.in
index 1139b98c4..383d17bcf 100644
--- a/src/sqlite.h.in
+++ b/src/sqlite.h.in
@@ -2619,7 +2619,7 @@ const char *sqlite3_sql(sqlite3_stmt *pStmt);
** then there is no distinction between protected and unprotected
** sqlite3_value objects and they can be used interchangeably. However,
** for maximum code portability it is recommended that applications
-** still make the distinction between between protected and unprotected
+** still make the distinction between protected and unprotected
** sqlite3_value objects even when not strictly required.
**
** ^The sqlite3_value objects that are passed as parameters into the