Assigning null to a key in the MultiDictionary will not delete that key (this behavior is symmetric with the behavior of querying the values under a key where null indicates that the key doesn't exist - it also doesn't add any "secret tricks" because the normal Dictionary doesn't intersect this functionality of having an extra container between the key and the values)

git-svn-id: file:///srv/devel/repo-conversion/nusu@217 d2e56fa2-650e-0410-a79f-9358c0239efd

Source/Collections/Deque.cs

@@ -35,7 +35,7 @@ namespace Nuclex.Support.Collections {
   ///   <para>
   ///     Therefore, it's not only good at coping with lists that are modified at their
   ///     beginning, but also at handling huge data sets since enlarging the deque doesn't
-  ///     require items to be copied around and still can be accessed by index.
+  ///     require items to be copied around and it still can be accessed by index.
   ///   </para>
   /// </remarks>
   public partial class Deque<ItemType> : IList<ItemType>, IList {