Resolved XMLDoc references for new overloads

With the addition of an optional `isExtendedAttribute` parameter to the `AttributeValueCollection.SetValue()` overload, and an optional `isDirty` parameter to the `RelatedTopicCollection.SetTopic()` overload, some XMLDoc references needed to be updated.

Author: JeremyCaney

OnTopic/Collections/RelatedTopicCollection.cs

@@ -40,7 +40,7 @@ public class RelatedTopicCollection : KeyedCollection<string, NamedTopicCollecti
     ///   with. This will be used when setting incoming relationships. In addition, a <see cref="RelatedTopicCollection"/> may
     ///   be set as <paramref name="isIncoming"/> if it is specifically intended to track incoming relationships; if this is not
     ///   set, then it will not allow incoming relationships to be set via the internal
-    ///   <see cref="SetTopic(String, Topic, Boolean)"/> overload.
+    ///   <see cref="SetTopic(String, Topic, Boolean, Boolean?)"/> overload.
     /// </remarks>
     public RelatedTopicCollection(Topic parent, bool isIncoming = false) : base(StringComparer.OrdinalIgnoreCase) {
       _parent = parent;

OnTopic/Topic.cs

@@ -643,7 +643,7 @@ public Topic? DerivedTopic {
     ///   called by the <see cref="AttributeValueCollection"/>. This is intended to enforce local business logic, and prevent
     ///   callers from introducing invalid data.To prevent a redirect loop, however, local properties need to inform the
     ///   <see cref="AttributeValueCollection"/> that the business logic has already been enforced. To do that, they must either
-    ///   call <see cref="AttributeValueCollection.SetValue(String, String, Boolean?, Boolean, DateTime?)"/> with the
+    ///   call <see cref="AttributeValueCollection.SetValue(String, String, Boolean?, Boolean, DateTime?, Boolean?)"/> with the
     ///   <c>enforceBusinessLogic</c> flag set to <c>false</c>, or, if they're in a separate assembly, call this overload.
     /// </remarks>
     /// <param name="key">The string identifier for the AttributeValue.</param>