Fix typos.

docs/articles/2.zeroql-v2.md

@@ -219,7 +219,7 @@ For ZeroQL it can be done via ZeroQL.CLI like that:
  dotnet zeroql queries extract -a .\bin\Debug\net6.0\TestProject.dll -c TestServer.Client.TestServerGraphQLClient -o ./queries
 ```
 
-The `` queries `` folder will contain a bunch of "hashed" GraphQL files. Inside they will have a GraphQL query assosiated hash in file name:
+The `` queries `` folder will contain a bunch of "hashed" GraphQL files. Inside they will have a GraphQL query associated hash in file name:
 
 ``` bash
 8cc1ee42eecdac2a8590486826856c041b04981a2c55d5cc560c338e1f6f0285.graphql # query GetUserQuery($id: Int!) { user(id: $id) { id firstName lastName } }
@@ -228,7 +228,7 @@ The `` queries `` folder will contain a bunch of "hashed" GraphQL files. Inside
 
 Then you need to configure your server to access them. How to do it for the HotChocolate server is described [here](https://chillicream.com/docs/hotchocolate/performance/persisted-queries).
 
-# Conclution
+# Conclusion
 
 That is all that I wanted to share right now. I would say it is a big release with improvements that extend the capabilities of ZeroQL. The support for file uploading, persisted queries, and request-like syntax opens possibilities for new workflows and optimizations.