Update docxml comments on BeInRange

It wasn't clear whether the values where inclusive or exclusive
fluentassertions · Apr 21, 2022 · 09dc7fd · 09dc7fd
1 parent d6b2d52
commit 09dc7fd
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/Src/FluentAssertions/Numeric/NumericAssertions.cs b/Src/FluentAssertions/Numeric/NumericAssertions.cs
@@ -292,10 +292,10 @@ public AndConstraint<TAssertions> BeLessThan(T expected, string because = "", pa
         /// Where the range is continuous or incremental depends on the actual type of the value.
         /// </remarks>
         /// <param name="minimumValue">
-        /// The minimum valid value of the range.
+        /// The minimum valid value of the range (inclusive).
         /// </param>
         /// <param name="maximumValue">
-        /// The maximum valid value of the range.
+        /// The maximum valid value of the range (inclusive).
         /// </param>
         /// <param name="because">
         /// A formatted phrase as is supported by <see cref="string.Format(string,object[])"/> explaining why the assertion