From 1bcb196ea966059566e437d32a7cc024b3c34ae0 Mon Sep 17 00:00:00 2001 From: Erik Wilde Date: Sat, 27 Oct 2018 15:05:00 +0200 Subject: [PATCH 1/2] minor clarification it's a bit confusing that both the id and the reference are called "operationId", so this tweak makes the text a bit more explicit. --- versions/3.0.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.0.3.md b/versions/3.0.3.md index 7920019331..4e2afb7890 100644 --- a/versions/3.0.3.md +++ b/versions/3.0.3.md @@ -2093,7 +2093,7 @@ solely by the existence of a relationship. ##### OperationRef Examples As references to `operationId` MAY NOT be possible (the `operationId` is an optional -value), references MAY also be made through a relative `operationRef`: +value in an [Operation Object](#operationObject)), references MAY also be made through a relative `operationRef`: ```yaml links: From 62c7f1e34e3d60229e943eb11619b223339e46e6 Mon Sep 17 00:00:00 2001 From: Ron Date: Fri, 14 Feb 2020 09:18:40 -0700 Subject: [PATCH 2/2] use right terminology Co-Authored-By: Mike Ralphson --- versions/3.0.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.0.3.md b/versions/3.0.3.md index 4e2afb7890..2daaf64f07 100644 --- a/versions/3.0.3.md +++ b/versions/3.0.3.md @@ -2093,7 +2093,7 @@ solely by the existence of a relationship. ##### OperationRef Examples As references to `operationId` MAY NOT be possible (the `operationId` is an optional -value in an [Operation Object](#operationObject)), references MAY also be made through a relative `operationRef`: +field in an [Operation Object](#operationObject)), references MAY also be made through a relative `operationRef`: ```yaml links: