Skip to content

Commit

Permalink
Fix spelling
Browse files Browse the repository at this point in the history
  • Loading branch information
openwindow authored and JeremySkinner committed Feb 10, 2020
1 parent e47e428 commit 3e58381
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/async.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

In some situations, you may wish to define asynchronous rules, for example when working with an external API. By default, FluentValidation allows custom rules defined with `MustAsync` or `CustomAsync` to be run asyhchronously, as well as defining asychronous coniditions with `WhenAsync`.

A simplistic solution that checks if a user ID is alrady in use using an external web API:
A simplistic solution that checks if a user ID is already in use using an external web API:

```csharp
public class CustomerValidator : AbstractValidator<Customer> {
Expand Down Expand Up @@ -31,4 +31,4 @@ var result = await validator.ValidateAsync(customer);
If your validator contains asynchronous validators or asynchronous conditions, it's important that you *always* call `ValidateAsync` on your validator and never `Validate`. If you call `Validate`, then your asynchronous rules *will be run synchronously*, which is not desirable.
You should not use asynchronous rules when `using automatic validation with ASP.NET <aspnet.html>`_ as ASP.NET's validation pipeline is not asynchronous. If you use asynchronous rules with ASP.NET's automatic validation, they will always be run synchronously.
```
```

0 comments on commit 3e58381

Please sign in to comment.