Remove misleading "always false" claim from Uri.UserEscaped documentation

Co-authored-by: gewarren <[email protected]>

Author: Copilot

xml/System/Uri.xml

@@ -6031,7 +6031,7 @@ The following examples show a URI and the results of calling <xref:System.Uri.Ge
 
 ## Remarks
 
-The <xref:System.Uri> constructors that have a `dontEscape` parameter have been obsolete since .NET Framework 2.0 and shouldn't be used. As a result, this property is deprecated and shouldn't be used either.
+The <xref:System.Uri.UserEscaped> property was originally designed to indicate that the string used to create the <xref:System.Uri> instance was completely escaped before it was passed to the constructor; that is, the `dontEscape` parameter of the constructor call was set to `true`. However, since the `dontEscape` parameter is now obsolete, this property is deprecated and shouldn't be used.
 
 ## Examples
  The following example creates a <xref:System.Uri> instance and determines whether it was fully escaped when it was created.