From ec7b27def50455ce2dfbf83c1bf7d65c0cda472f Mon Sep 17 00:00:00 2001 From: Aramis Date: Fri, 8 Dec 2023 12:27:56 -0500 Subject: [PATCH] fix typos Signed-off-by: Aramis --- docs/openapi/01-getting-started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/openapi/01-getting-started.md b/docs/openapi/01-getting-started.md index b1a6e0c224..4e4c466572 100644 --- a/docs/openapi/01-getting-started.md +++ b/docs/openapi/01-getting-started.md @@ -9,8 +9,8 @@ Difficulty: Medium The goal of this tutorial is to more tightly couple your OpenAPI specification and plugin lifecycle. The OpenAPI tooling project area has created tools that allow you to create, 1. A typed `express` router that provides strong guardrails during development for input and output values. Support for query, path parameters and request body, as well as experimental support for headers and cookies. -2. An autogenerated client to interact with your plugin's backend. Support for all request types, parameters and body, as well as return types. Provides a low-level interface to allow more customization by higher level libraries. -3. Validation and verifaction tooling to ensure your API and specification stay in sync. Includes testing against your unit tests. +2. An auto-generated client to interact with your plugin's backend. Support for all request types, parameters and body, as well as return types. Provides a low-level interface to allow more customization by higher level libraries. +3. Validation and verification tooling to ensure your API and specification stay in sync. Includes testing against your unit tests. ## Prerequisites