Skip to content

Commit 44e9d30

Browse files
Fixed typo and minor gramar (#898)
1 parent b0ee204 commit 44e9d30

File tree

2 files changed

+14
-14
lines changed

2 files changed

+14
-14
lines changed

site/code/index.html.js

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ In addition to the GraphQL [reference implementations in JavaScript](#javascript
4747
4848
### C# / .NET
4949
50-
#### [graphql-dotnet](https://github.com/graphql-dotnet/graphql-dotnet): GraphQL for .NET
50+
#### [graphql-dotnet](https://github.com/graphql-dotnet/graphql-dotnet): GraphQL for .NET.
5151
5252
\`\`\`csharp
5353
using System;
@@ -75,10 +75,10 @@ public class Program
7575
}
7676
\`\`\`
7777
78-
- [graphql-net](https://github.com/ckimes89/graphql-net): Convert GraphQL to IQueryable
79-
- [Entity GraphQL](https://github.com/lukemurray/EntityGraphQL): .NET Core GraphQL library. Compiles to IQueryable to easily expose a schema from an existing data model (E.g. from an Entity Framework data model)
80-
- [DotNetGraphQLQueryGen](https://github.com/lukemurray/DotNetGraphQLQueryGen): .NET Core library to generate classes from a GraphQL schema for type-safe querying in dotnet
81-
- [Hot Chocolate](https://github.com/ChilliCream/hotchocolate): GraphQL Server for .NET core and .NET classic
78+
- [graphql-net](https://github.com/ckimes89/graphql-net): Convert GraphQL to IQueryable.
79+
- [Entity GraphQL](https://github.com/lukemurray/EntityGraphQL): .NET Core GraphQL library. Compiles to IQueryable to easily expose a schema from an existing data model (E.g. from an Entity Framework data model).
80+
- [DotNetGraphQLQueryGen](https://github.com/lukemurray/DotNetGraphQLQueryGen): .NET Core library to generate classes from a GraphQL schema for type-safe querying in dotnet.
81+
- [Hot Chocolate](https://github.com/ChilliCream/hotchocolate): GraphQL Server for .NET core and .NET classic.
8282
8383
### Clojure
8484
@@ -176,14 +176,14 @@ A full implementation of the GraphQL specification that aims to maintain externa
176176
- Provides a controller to receive and respond to GraphQL requests through HTTP, based on their guidelines.
177177
- Generates the schema at startup with spring bean configuration to make it easy to extend.
178178
- Includes a [GraphiQL](https://github.com/graphql/graphiql) browser enabled by default in development. The browser is accessible at /graphql/browser.
179-
- Overrides the default data binder to use the data binding provided by Grails
180-
- Provides a [trait](https://grails.github.io/gorm-graphql/latest/api/org/grails/gorm/graphql/plugin/testing/GraphQLSpec.html) to make integration testing of your GraphQL endpoints easier
179+
- Overrides the default data binder to use the data binding provided by Grails.
180+
- Provides a [trait](https://grails.github.io/gorm-graphql/latest/api/org/grails/gorm/graphql/plugin/testing/GraphQLSpec.html) to make integration testing of your GraphQL endpoints easier.
181181
182182
See [the documentation](https://grails.github.io/gorm-graphql/latest/guide/index.html) for more information.
183183
184184
#### [GQL](https://grooviter.github.io/gql/)
185185
186-
GQL is a Groovy library for GraphQL
186+
GQL is a Groovy library for GraphQL.
187187
188188
### Java
189189
@@ -349,11 +349,11 @@ Apollo Server also supports all Node.js HTTP server frameworks: Express, Connect
349349
350350
### PHP
351351
352-
- [graphql-php](https://github.com/webonyx/graphql-php): A PHP port of GraphQL reference implementation
352+
- [graphql-php](https://github.com/webonyx/graphql-php): A PHP port of GraphQL reference implementation.
353353
- [graphql-relay-php](https://github.com/ivome/graphql-relay-php): A library to help construct a graphql-php server supporting react-relay.
354354
- [Railt](https://github.com/railt/railt): A PHP GraphQL Framework.
355-
- [Lighthouse](https://github.com/nuwave/lighthouse): A GraphQL server for Laravel
356-
- [GraphQLBundle](https://github.com/overblog/GraphQLBundle): A GraphQL server for Symfony
355+
- [Lighthouse](https://github.com/nuwave/lighthouse): A GraphQL server for Laravel.
356+
- [GraphQLBundle](https://github.com/overblog/GraphQLBundle): A GraphQL server for Symfony.
357357
- [WPGraphQL](https://github.com/wp-graphql/wp-graphql): A free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site
358358
359359
#### [API Platform](https://api-platform.com) ([github](https://github.com/api-platform/api-platform))
@@ -577,7 +577,7 @@ sleep
577577
578578
### Rust
579579
580-
- [graphql-rust/juniper](https://github.com/graphql-rust/juniper): GraphQL server library for Rust
580+
- [graphql-rust/juniper](https://github.com/graphql-rust/juniper): GraphQL server library for Rust.
581581
582582
### Scala
583583
@@ -624,7 +624,7 @@ Executor.execute(schema, query) map println
624624
625625
- [GraphQL.Client](https://github.com/graphql-dotnet/graphql-client): A GraphQL Client for .NET.
626626
- [graphql-net-client](https://github.com/bkniffler/graphql-net-client): Basic example GraphQL client for .NET.
627-
- [SAHB.GraphQLClient](https://github.com/sahb1239/SAHB.GraphQLClient): GraphQL client which supports generating queries from C# classes
627+
- [SAHB.GraphQLClient](https://github.com/sahb1239/SAHB.GraphQLClient): GraphQL client which supports generating queries from C# classes.
628628
629629
### Clojurescript
630630

site/learn/BestPractice-ThinkingInGraphs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Graphs are powerful tools for modeling many real-world phenomena because they re
1414
## Shared Language
1515
> Naming things is a hard but important part of building intuitive APIs
1616
17-
Think of your GraphQL schema as an expressive shared language for your team and your users. To build a good schema, examine the everyday language you use to describe your business. For example, let's try to describe an email app in plain english:
17+
Think of your GraphQL schema as an expressive shared language for your team and your users. To build a good schema, examine the everyday language you use to describe your business. For example, let's try to describe an email app in plain English:
1818

1919
* A user can have multiple email accounts
2020
* Each email account has an address, inbox, drafts, deleted items, and sent items

0 commit comments

Comments
 (0)