Add note about middleware order

website/src/docs/hotchocolate/defining-a-schema/mutations.md

@@ -141,6 +141,10 @@ public class Startup
 >
 > [Learn more about extending types](/docs/hotchocolate/defining-a-schema/extending-types)
 
+A mutation type is just a regular object type, so everything that applies to an object type also applies to the mutation type (this is true for all root types).
+
+[Learn more about object types](/docs/hotchocolate/defining-a-schema/object-types)
+
 # Transactions
 
 With multiple mutations executed serially in one request it can be useful to wrap these in a transaction that we can control.

website/src/docs/hotchocolate/defining-a-schema/queries.md

@@ -144,4 +144,6 @@ public class Startup
 >
 > [Learn more about extending types](/docs/hotchocolate/defining-a-schema/extending-types)
 
-A query type is just a regular [object type](/docs/hotchocolate/defining-a-schema/object-types), so we can do everything we could do with an object type with the query type (this applies to all root types).
+A query type is just a regular object type, so everything that applies to an object type also applies to the query type (this is true for all root types).
+
+[Learn more about object types](/docs/hotchocolate/defining-a-schema/object-types)

website/src/docs/hotchocolate/defining-a-schema/subscriptions.md

@@ -130,6 +130,10 @@ public class Startup
 >
 > [Learn more about extending types](/docs/hotchocolate/defining-a-schema/extending-types)
 
+A subscription type is just a regular object type, so everything that applies to an object type also applies to the subscription type (this is true for all all root types).
+
+[Learn more about object types](/docs/hotchocolate/defining-a-schema/object-types)
+
 # Transport
 
 After defining the subscription type, we need to add the WebSockets middleware to our request pipeline.

website/src/docs/hotchocolate/integrations/entity-framework.md

@@ -15,7 +15,7 @@ When using `services.AddDbContext<T>` to register a `DbContext` as a scoped serv
 - `A second operation started on this context before a previous operation completed.`
 - `Cannot access a disposed object.`
 
-Fortunatley there are a couple of solutions that can be used to avoid the described issue. We will take a closer look at them in the below sections.
+Fortunately there are a couple of solutions that can be used to avoid the described issue. We will take a closer look at them in the below sections.
 
 # DbContextFactory
 
@@ -83,8 +83,10 @@ We can make this even simpler, by creating an attribute inheriting from the `Use
 ```csharp
 public class UseSomeDbContext : UseDbContextAttribute
 {
-    public UseSomeDbContext() : base(typeof(SomeDbContext))
+    public UseSomeDbContext([CallerLineNumber] int order = 0)
+        : base(typeof(SomeDbContext))
     {
+        Order = order;
     }
 }
 
@@ -96,6 +98,8 @@ public class Query
 }
 ```
 
+> Note: Since the [order of attributes is not guaranteed by .NET](https://docs.microsoft.com/dotnet/csharp/language-reference/language-specification/attributes#attribute-specification), Hot Chocolate uses the line number to determine the correct order of the Data middleware. If you are using a custom attribute, you have to forward the line number using the `CallerLineNumberAttribute`.
+
 </ExampleTabs.Annotation>
 <ExampleTabs.Code>