manual.texi fix for colons in TIME being referred to as semicolons

Docs/manual.texi:
  fix for colons in TIME being referred to as semicolons

1 files changed, 2 insertions, 2 deletions

diff --git a/Docs/manual.texi b/Docs/manual.texi
index ad2bae3a0bb..2759e78e568 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -28935,14 +28935,14 @@ seconds values that are less than @code{10}.  @code{'8:3:2'} is the same as
 @code{'08:03:02'}.
 
 Be careful about assigning ``short'' @code{TIME} values to a @code{TIME}
-column. Without semicolon, MySQL interprets values using the 
+column. Without colons, MySQL interprets values using the 
 assumption that the rightmost digits represent seconds. (MySQL 
 interprets @code{TIME} values as elapsed time rather than as time of 
 day.) For example, you might think of @code{'1112'} and @code{1112} as 
 meaning @code{'11:12:00'} (12 minutes after 11 o'clock), but
 MySQL interprets them as @code{'00:11:12'} (11 minutes, 12 seconds).
 Similarly, @code{'12'} and @code{12} are interpreted as @code{'00:00:12'}.
-@code{TIME} values with semicolon, instead, are always treated as
+@code{TIME} values with colons, by contrast, are always treated as
 time of the day. That is @code{'11:12'} will mean @code{'11:12:00'},
 not @code{'00:11:12'}.