Small. Fast. Reliable.
Choose any three.
*** 106,112 ****
  
  *: *Stand-in for an enterprise database during demos or testing*
  
! _: If you are writting a client application for an enterprise database engine,
  it makes sense to use a generic database backend that allows you to connect
  to many different kinds of SQL database engines.  It makes even better
  sense to
--- 106,112 ----
  
  *: *Stand-in for an enterprise database during demos or testing*
  
! _: If you are writing a client application for an enterprise database engine,
  it makes sense to use a generic database backend that allows you to connect
  to many different kinds of SQL database engines.  It makes even better
  sense to
***************
*** 163,169 ****
  *: *High-volume Websites*
  
  _: SQLite will normally work fine as the database backend to a website.
! But if you website is so busy that your are thinking of splitted the
  database component off onto a separate machine, then you should 
  definitely consider using an enterprise-class client/server database
  engine instead of SQLite.
--- 163,169 ----
  *: *High-volume Websites*
  
  _: SQLite will normally work fine as the database backend to a website.
! But if your website is so busy that you are thinking of splitting the
  database component off onto a separate machine, then you should 
  definitely consider using an enterprise-class client/server database
  engine instead of SQLite.