@@ 14,7 14,7 @@
* The @code{Multicast_Socket_FD} tagged type derives from the
* @code{Socket_FD} type. It gets initialized by calling
* @ref{Create_Multicast_Socket (function)}. An uninitialized
- * @code{Multicast_Socket_FD} can be succesfully compared to
+ * @code{Multicast_Socket_FD} can be successfully compared to
* @code{Null_Multicast_Socket_FD}.
=*/
@@ 13,7 13,7 @@
* doc:
* The @code{Socket_FD} tagged type is the root type of all
* sockets. It gets initialized by calling @ref{Socket (procedure)}.
- * An uninitialized @code{Socket_FD} can be succesfully compared to
+ * An uninitialized @code{Socket_FD} can be successfully compared to
* @code{Null_Socket_FD}.
=*/
@@ 167,7 167,7 @@
* Note that unlike their C language counterpart, @code{Getsockopt}
* and @code{Setsockopt} do not require an extra parameter
* representing the length in bytes of the option value. AdaSockets
- * nows the right size for every option.
+ * knows the right size for every option.
* concept: Manipulating socket options
* concept: Retrieving socket options
* see: Setsockopt (procedure)
@@ 215,7 215,7 @@
* Note that unlike their C language counterpart, @code{Getsockopt}
* and @code{Setsockopt} do not require an extra parameter
* representing the length in bytes of the option value. AdaSockets
- * nows the right size for every option.
+ * knows the right size for every option.
* concept: Manipulating socket options
* concept: Setting socket options
* see: Getsockopt (procedure)
@@ 300,7 300,7 @@
* TCP socket. Only one system call will be performed; this
* function will return whatever data has arrived. Note that in
* GNAT the secondary stack may be used to store the data and may
- * result in stack storage exhaustion.
+ * result in stack storage exhaustion.
* concept: Receiving data
* exc:
* Connection_Closed, Peer has closed the connection before sending any data
@@ 441,12 441,12 @@
* As soon that at least one character is available, the current
* reception buffer is returned.
*
- * There is usually little gain in using this function whose behaviour is
+ * There is usually little gain in using this function whose behavior is
* comparable to the one of @ref{Receive (function)}. Other
* functions such as @ref{Get_Char (function)}, or
* @ref{Get_Line (function)}, allow more structured programming.
*
- * However, this function may be used to avoid loosing characters
+ * However, this function may be used to avoid losing characters
* when calling @ref{Unset_Buffer (procedure)}, if, for some reason,
* the remote host may have sent some.
* concept: Receiving data
@@ 558,7 558,7 @@
* kind: procedure
* arg: Socket, in, Socket_FD'Class,, Initialized and connected socket object
* doc:
- * This procedure deinstalls the buffer previously installed by
+ * This procedure uninstalls the buffer previously installed by
* @ref{Set_Buffer (procedure)}. If any data is still present in
* the buffer, it will be lost. To avoid this situation, the buffer
* can be flushed by calling @ref{Get (function)}.