update docs (v13/enums.md, 2023-08-15-fusion.md)

website/src/blog/2023-08-15-fusion/2023-08-15-fusion.md

@@ -28,7 +28,7 @@ Up to this point, the GraphQL landscape has lacked an open specification tailore
 
 ## Let's share and compete
 
-Late last year, [ChilliCream](https://chillicream.com) and [The Guild](https://the-guild.dev/) met in Paris and discussed their approaches towards distributed GraphQL. It became clear that both companies were solving similar problems, and we decided to join forces on this project. ChilliCream would provide the initial work on the Fusion spec and implementation. At the same time, The Guild would start specifying their work on [GraphQL Mesh Gateway](https://the-guild.dev/graphql/mesh) with [OpenAPI support](https://the-guild.dev/graphql/mesh/docs/handlers/openapi) and help shape the initial Fusion spec. [WunderGraph](https://wundergraph.com/) has joind this effort to implement a Fusion-compatible Gateway and also contribute to the GraphQL-Fusion spec.
+Late last year, [ChilliCream](https://chillicream.com) and [The Guild](https://the-guild.dev/) met in Paris and discussed their approaches towards distributed GraphQL. It became clear that both companies were solving similar problems, and we decided to join forces on this project. ChilliCream would provide the initial work on the Fusion spec and implementation. At the same time, The Guild would start specifying their work on [GraphQL Mesh Gateway](https://the-guild.dev/graphql/mesh) with [OpenAPI support](https://the-guild.dev/graphql/mesh/docs/handlers/openapi) and help shape the initial Fusion spec. [WunderGraph](https://wundergraph.com/) has joined this effort to implement a Fusion-compatible Gateway and also contribute to the GraphQL-Fusion spec.
 
 Today, we are thrilled to unveil GraphQL-Fusion, an open specification under the **MIT license**. This initiative empowers everyone to craft tools and solutions centered around distributed GraphQL services. Complementing this announcement, we're also introducing Hot Chocolate Fusion, an early implementation of the GraphQL-Fusion spec draft. The aim for the GraphQL-Fusion spec is to create an open specification that we will propose to the GraphQL Foundation Composite Schemas working group.
 

website/src/docs/hotchocolate/v13/defining-a-schema/enums.md

@@ -316,7 +316,7 @@ public class UserRoleType : EnumType<UserRole>
 
 Unless specified explicitly, Hot Chocolate automatically infers the names of enums and their values. Per default the name of the enum becomes the name of the enum type. When using `EnumType<T>` in Code-first, the name of `T` is chosen as the name for the enum type.
 
-Enum values are automatically formatted to the UPPER_SNAIL_CASE according to the GraphQL specification:
+Enum values are automatically formatted to the UPPER_SNAKE_CASE according to the GraphQL specification:
 
 - `Guest` becomes `GUEST`
 - `HeadOfDepartment` becomes `HEAD_OF_DEPARTMENT`