Fix a few for xml doc comment of CloseStatusCode.cs

websocket-sharp/CloseStatusCode.cs

@@ -31,7 +31,7 @@ using System;
 namespace WebSocketSharp
 {
   /// <summary>
-  /// Contains the values of the status code for the WebSocket connection closure.
+  /// Contains the values of the status code for the WebSocket connection close.
   /// </summary>
   /// <remarks>
   ///   <para>
@@ -40,16 +40,16 @@ namespace WebSocketSharp
   ///   of RFC 6455.
   ///   </para>
   ///   <para>
-  ///   "Reserved value" must not be set as a status code in a close control frame by
-  ///   an endpoint. It's designated for use in applications expecting a status code
-  ///   to indicate that the connection was closed due to a system grounds.
+  ///   "Reserved value" must not be set as a status code in a close control frame
+  ///   by an endpoint. It's designated for use in applications expecting a status
+  ///   code to indicate that the connection was closed due to the system grounds.
   ///   </para>
   /// </remarks>
   public enum CloseStatusCode : ushort
   {
     /// <summary>
     /// Equivalent to close status 1000.
-    /// Indicates a normal closure.
+    /// Indicates a normal close.
     /// </summary>
     Normal = 1000,
     /// <summary>
@@ -64,8 +64,8 @@ namespace WebSocketSharp
     ProtocolError = 1002,
     /// <summary>
     /// Equivalent to close status 1003.
-    /// Indicates that an endpoint is terminating the connection because it has received an
-    /// unacceptable type message.
+    /// Indicates that an endpoint is terminating the connection because it has received
+    /// an unacceptable type message.
     /// </summary>
     IncorrectData = 1003,
     /// <summary>
@@ -85,33 +85,33 @@ namespace WebSocketSharp
     Abnormal = 1006,
     /// <summary>
     /// Equivalent to close status 1007.
-    /// Indicates that an endpoint is terminating the connection because it has received a message
-    /// that contains a data that isn't consistent with the type of the message.
+    /// Indicates that an endpoint is terminating the connection because it has received
+    /// a message that contains a data that isn't consistent with the type of the message.
     /// </summary>
     InconsistentData = 1007,
     /// <summary>
     /// Equivalent to close status 1008.
-    /// Indicates that an endpoint is terminating the connection because it has received a message
-    /// that violates its policy.
+    /// Indicates that an endpoint is terminating the connection because it has received
+    /// a message that violates its policy.
     /// </summary>
     PolicyViolation = 1008,
     /// <summary>
     /// Equivalent to close status 1009.
-    /// Indicates that an endpoint is terminating the connection because it has received a message
-    /// that is too big to process.
+    /// Indicates that an endpoint is terminating the connection because it has received
+    /// a message that is too big to process.
     /// </summary>
     TooBig = 1009,
     /// <summary>
     /// Equivalent to close status 1010.
-    /// Indicates that the client is terminating the connection because it has expected the server
-    /// to negotiate one or more extension, but the server didn't return them in the handshake
-    /// response.
+    /// Indicates that the client is terminating the connection because it has expected
+    /// the server to negotiate one or more extension, but the server didn't return them
+    /// in the handshake response.
     /// </summary>
     IgnoreExtension = 1010,
     /// <summary>
     /// Equivalent to close status 1011.
-    /// Indicates that the server is terminating the connection because it has encountered an
-    /// unexpected condition that prevented it from fulfilling the request.
+    /// Indicates that the server is terminating the connection because it has encountered
+    /// an unexpected condition that prevented it from fulfilling the request.
     /// </summary>
     ServerError = 1011,
     /// <summary>