Relase v5.25

FastEndpoints · May 2, 2024 · e243f50 · e243f50
1 parent c33bd33
commit e243f50
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/Src/Directory.Build.props b/Src/Directory.Build.props
@@ -1,7 +1,7 @@
 <Project>
  <PropertyGroup>
 
- <Version>5.24.0.12-beta</Version>
+ <Version>5.25.0</Version>
 
  <TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
  <LangVersion>latest</LangVersion>

diff --git a/Src/Library/changelog.md b/Src/Library/changelog.md
@@ -106,7 +106,7 @@ bld.WebHost.ConfigureKestrel(
  });
 ```
 
-If the incoming request body size is more than `MaxRequestBodySize`, Kestrel would automatically short-circuit the response with a `413 - Content Too Long` response, which may not be what you want. You can instead specify a `FormExceptionTrasnformer` func to transform the exception in to a regular 400 error/problem details JSON response like so:
+If the incoming request body size is more than `MaxRequestBodySize`, Kestrel would automatically short-circuit the request with a `413 - Content Too Long` response, which may not be what you want. You can instead specify a `FormExceptionTrasnformer` func to transform the exception in to a regular 400 error/problem details JSON response like so:
 
 ```csharp
 app.UseFastEndpoints(
@@ -157,7 +157,7 @@ public class MyAppFixture : AppFixture<Program> { ... }
 
 <details><summary>Contention issue resulting in random 415 responses</summary>
 
-There was a possible contention issue that could arise in and extremely niche edge case where the WAFs could be instantiated in quick succession which results in tests failing due to 415 responses being returned randomly. This has been fixed by moving the necessary work to be performed at app startup instead of at the first request for a particular endpoint. More info: #661
+There was a possible contention issue that could arise in an extremely niche edge case where the WAFs could be instantiated in quick succession which results in tests failing due to 415 responses being returned randomly. This has been fixed by moving the necessary work to be performed at app startup instead of at the first request for a particular endpoint. More info: #661
 
 </details>