manual.texi:

chow -> show


Docs/manual.texi:
  Monty: chow -> show

Docs/manual.texi

@@ -28413,18 +28413,18 @@ aren't specified.  Another way to around this bug is to upgrade to
 MyODBC 2.50.33 and @strong{MySQL} 3.23.x, which together provides a
 workaround for this bug!
 @item
-Set the `Return matching rows' MyODBC option field when connecting to
+Set the ``Return matching rows'' MyODBC option field when connecting to
 @strong{MySQL}.
 @item
 You should have a primary key in the table;  If not, new or updated rows
-may chow up as @code{#Deleted#}.
+may show up as @code{#Deleted#}.
 @item
 You should have a timestamp in all tables you want to be able to update.
 For maximum portability @code{TIMESTAMP(14)} or simple @code{TIMESTAMP}
 is recommended instead of other @code{TIMESTAMP(X)} variations.
 @item
 Only use double float fields. Access fails when comparing with single floats.
-The symptom usually is that new or updated rows may chow up as @code{#Deleted#}
+The symptom usually is that new or updated rows may show up as @code{#Deleted#}
 or that you can't find or update rows.
 @item
 If you still get the error @code{Another user has changed your data} after