From 19eada89b15074ef9d397d46d7d864f9ec8d0919 Mon Sep 17 00:00:00 2001 From: Michael Staib Date: Tue, 17 Nov 2020 10:37:28 +0100 Subject: [PATCH] formatting --- .../docs/hotchocolate/api-reference/migrate-from-10-to-11.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md b/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md index d48b0bf17e2..aa57122f8ac 100644 --- a/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md +++ b/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md @@ -20,7 +20,7 @@ We have now added the most common packages to the Hot Chocolate core. But there | HotChocolate.PersistedQueries.FileSystem | This package provides a persisted query storage for the file system. | | HotChocolate.PersistedQueries.Redis | This package provides a persisted query storage for Redis. | -# Startup +# ASP.NET Core One of the main focuses of version 11 was to create a new configuration API that brings all our builders together into one unified API. This also means that we had to introduce breaking changes to the way we configure schemas. @@ -67,7 +67,7 @@ services .ModifyRequestOptions(o => o.ExecutionTimeout = TimeSpan.FromSeconds(180)); ``` -# Configure +## Configure After migrating the schema configuration, the next area that has fundamentally changed is the schema middleware.