diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
| commit | 8b4ff8b6a14096a28910fbff3d485f30dcb9a637 (patch) | |
| tree | c250f17f4a8e3bfee442970a0666431ed8310650 /src/interfaces/libpq/win32.c | |
| parent | baaec74c5a953032049015883802660edd821cac (diff) | |
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Diffstat (limited to 'src/interfaces/libpq/win32.c')
| -rw-r--r-- | src/interfaces/libpq/win32.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/interfaces/libpq/win32.c b/src/interfaces/libpq/win32.c index 0ce8a252366..6d147712070 100644 --- a/src/interfaces/libpq/win32.c +++ b/src/interfaces/libpq/win32.c @@ -110,7 +110,7 @@ static struct WSErrorEntry WSAEADDRINUSE, "Address already in use" }, { - WSAEADDRNOTAVAIL, "Can't assign requested address" + WSAEADDRNOTAVAIL, "Cannot assign requested address" }, { WSAENETDOWN, "Network is down" @@ -137,10 +137,10 @@ static struct WSErrorEntry WSAENOTCONN, "Socket is not connected" }, { - WSAESHUTDOWN, "Can't send after socket shutdown" + WSAESHUTDOWN, "Cannot send after socket shutdown" }, { - WSAETOOMANYREFS, "Too many references, can't splice" + WSAETOOMANYREFS, "Too many references, cannot splice" }, { WSAETIMEDOUT, "Connection timed out" |