Minor doc updates

FluentValidation · Feb 22, 2020 · 84670ab · 84670ab
1 parent 3060c48
commit 84670ab
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/docs/built-in-validators.md b/docs/built-in-validators.md
@@ -272,6 +272,11 @@ From the comments:
 
 Alternatively, you can use the old email validation behaviour that uses a regular expression consistent with the .NET 4.x version of the ASP.NET `EmailAddressAttribute`. You can use this behaviour in FluentValidation by calling `RuleFor(x => x.Email).EmailAddress(EmailValidationMode.Net4xRegex)`. Note that this approach is deprecated and will generate a warning as regex-based email validation is not recommended. 
 
+```eval_rst
+.. note::
+  In FluentValidation 9, the ASP.NET Core-compatible "simple" check is the default mode. In FluentValidation 8.x (and older), the Regex mode is the default.
+```
+
 ## Credit Card Validator
 Checks whether a string property could be a valid credit card number. 
 

diff --git a/docs/upgrading-to-9.md b/docs/upgrading-to-9.md
@@ -54,7 +54,7 @@ FluentValidation 4.x-8.x contained a bug where using `NotEqual`/`Equal` on strin
 
 ### Transform updates
 
-The `Transform` method can now be used to transform a property value to a different type prior to validation occurring. [See the documentation for further details.](transform.html)
+The `Transform` method can now be used to transform a property value to a different type prior to validation occurring. [See the documentation for further details.](transform)
 
 ### Severity with callback