Skip to content

Commit e6ead14

Browse files
authored
Spelling fixes in readme
1 parent 80f3e86 commit e6ead14

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ implementation samples don't account for various common use cases like BatchRequ
2424

2525
### NOTES:
2626
1. **NOTE:** According to the HotChocolate team on Slack, they will provide an Official AzureFunctions
27-
middleware as part of v11. :-)
28-
2. **WARNING: Very Limited Testing has been done on this but I am actively using it on projects,
27+
middleware as part of v11 (eventually). :-)
28+
2. **WARNING: Limited Testing has been done on this but I am actively using it on projects,
2929
and will update with any findings.**
3030

3131
## Goals
@@ -37,11 +37,11 @@ painless and simple as possible *(with a few design assumptions aside)*.
3737
* Keep this adaptation layer as lean and DRY as possible while also supporting as much OOTB
3838
functionality as possible.
3939
* Ensures that the Azure Functions paradigm and flexibility are not lost, so that all OOTB
40-
C# bindings, DI, and current Function invokation are maintained.
40+
C# bindings, DI, and current Function invocation are maintained.
4141

4242
## Implementation:
4343
This approach uses a "Middleware Proxy" pattern whereby we provide the functionality of the
44-
middleware via a proxy class that can be injected into the Azure Function,
44+
HotChocolate HTTP middleware via a proxy class that can be injected into the Azure Function,
4545
but otherwise do not change the existing AzureFunctions invocation pipeline.
4646

4747
This Proxy exposes an "executor" interface that can process the HttpContext in an AzureFunction.

0 commit comments

Comments
 (0)