Fix trivial warnings.

Author: yfakariya

src/MsgPack/BufferedStream.cs

@@ -44,14 +44,14 @@ namespace System.IO
 	/// greater than the internal buffer size, then this class may not even allocate the internal buffer.
 	/// See a large comment in Write for the details of the write buffer heuristic.
 	/// 
-	/// This class buffers reads & writes in a shared buffer.
+	/// This class buffers reads & writes in a shared buffer.
 	/// (If you maintained two buffers separately, one operation would always trash the other buffer
 	/// anyways, so we might as well use one buffer.) 
 	/// The assumption here is you will almost always be doing a series of reads or writes, but rarely
 	/// alternate between the two of them on the same stream.
 	///
 	/// Class Invariants:
-	/// The class has one buffer, shared for reading & writing.
+	/// The class has one buffer, shared for reading & writing.
 	/// It can only be used for one or the other at any point in time - not both.
 	/// The following should be true:
 	/// <![CDATA[

src/MsgPack/PackerUnpackerStreamOptions.cs

@@ -1,4 +1,4 @@
-#region -- License Terms --
+#region -- License Terms --
 //
 // MessagePack for CLI
 //
@@ -82,18 +82,18 @@ private static bool ShouldWrapStream( Stream stream )
 		///			as long as it has buffered value.
 		///		</para>
 		///		<para>
-		///			Current built-in <see cref="Unpacker"/> implementation uses <see cref="BufferedStream"/> for buffering,
+		///			Current built-in <see cref="Unpacker"/> implementation uses <c>BufferedStream</c> for buffering,
 		///			and avoid buffering for following in-memory or stream with buffering feature:
 		///			<list type="bullet">
-		///				<item><see cref="System.IO.BufferedStream" /> itself.</item>
-		///				<item><see cref="System.IO.MemoryStream" />.</item>
-		///				<item><see cref="System.IO.UnmanagedMemoryStream" />.</item>
-		///				<item><see cref="System.IO.FileStream" /> which has own internal buffer.</item>
+		///				<item><c>System.IO.BufferedStream</c> itself.</item>
+		///				<item><c>System.IO.MemoryStream</c>.</item>
+		///				<item><c>System.IO.UnmanagedMemoryStream</c>.</item>
+		///				<item><c>System.IO.FileStream</c> which has own internal buffer.</item>
 		///			</list>
 		///		</para>
 		///		<para>
-		///			Logically, it is preferred that you should wrap with <see cref="System.IO.BufferedStream"/> yourself for underlying stream
-		///			for wrapper stream such as <seealso cref="System.IO.Compression.DeflateStream"/>, <see cref="System.Security.Cryptography.CryptoStream"/>, etc.
+		///			Logically, it is preferred that you should wrap with <c>System.IO.BufferedStream</c> yourself for underlying stream
+		///			for wrapper stream such as <c>System.IO.Compression.DeflateStream</c>, <c>System.Security.Cryptography.CryptoStream</c>, etc.
 		///		</para>
 		/// </remarks>
 		/// <seealso cref="BufferSize"/>

src/MsgPack/Serialization/MessagePackSerializer`1.cs

@@ -527,7 +527,7 @@ protected internal virtual Task PackToAsyncCore( Packer packer, T objectTree, Ca
 		///			The implementation of this class returns <c>null</c> for nullable types (that is, all reference types and <see cref="Nullable{T}"/>); otherwise, throws <see cref="System.Runtime.Serialization.SerializationException"/>.
 		///		</para>
 		///		<para>
-		///			Custom serializers can override this method to provide custom nil representation. For example, built-in <see cref="DBNull"/> serializer overrides this method to return <see cref="DBNull.Value"/> instead of <c>null</c>.
+		///			Custom serializers can override this method to provide custom nil representation. For example, built-in <c>DBNull</c> serializer overrides this method to return <c>DBNull.Value</c> instead of <c>null</c>.
 		///		</para>
 		/// </remarks>
 		protected internal virtual T UnpackNil()

src/MsgPack/Serialization/PackHelpers.cs

@@ -1,4 +1,4 @@
-#region -- License Terms --
+#region -- License Terms --
 //
 // MessagePack for CLI
 //
@@ -312,7 +312,7 @@ IDictionary<string, Action<Packer, TObject>> operations
 		///		<see cref="PackToMapParameters{T}.Packer"/> of <paramref name="parameter"/> is <c>null</c>.
 		/// </exception>
 		/// <exception cref="ArgumentException">
-		///		<see cref="PackToMapAsyncParameters{T}.Operations"/> of <paramref name="parameter"/> is <c>null</c>.
+		///		<c>PackToMapAsyncParameters{T}.Operations</c> of <paramref name="parameter"/> is <c>null</c>.
 		/// </exception>
 #if !UNITY || MSGPACK_UNITY_FULL
 		[EditorBrowsable( EditorBrowsableState.Never )]

src/MsgPack/Serialization/SerializationCompatibilityOptions.cs

@@ -106,7 +106,7 @@ public PackerCompatibilityOptions PackerCompatibilityOptions
 		/// </value>
 		/// <remarks>
 		///		Historically, MessagePack for CLI ignored packability interfaces (<see cref="IPackable"/>, <see cref="IUnpackable"/>, 
-		///		<see cref="IAsyncPackable"/> and <see cref="IAsyncUnpackable"/>) for collection which implements <see cref="IEquatable{T}"/> (except <see cref="String"/> and its kinds).
+		///		<c>IAsyncPackable"</c> and <c>IAsyncUnpackable</c>) for collection which implements <see cref="IEquatable{T}"/> (except <see cref="String"/> and its kinds).
 		///		As of 0.7, the generator respects such interfaces even if the target type is collection.
 		///		Although this behavior is desirable and correct, setting this property <c>true</c> turn out the new behavior for backward compatibility.
 		/// </remarks>