Skip to content

Commit 5669bd4

Browse files
committed
More content fixes
1 parent e622056 commit 5669bd4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

guidelines/REUSE.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ The following types are reusable, as defined by the spec:
1515

1616
When authoring API design documents, common object definitions can be utilized to avoid duplication. For example, imagine multiple path definitions that each share a common path parameter, or a common response structure. The OpenAPI specification allows reuse of common object definitions through the use of "references".
1717

18-
A reference a construct in your API design document that indicates "the content for this portion of the document is defined elsewhere". To create a reference, at the location in your document where you want to reuse some other definition, create an object that has a `$ref` property whose value is a URI pointing to where the definition is (more on this in later sections).
18+
A reference is a construct in your API design document that indicates "the content for this portion of the document is defined elsewhere". To create a reference, at the location in your document where you want to reuse some other definition, create an object that has a `$ref` property whose value is a URI pointing to where the definition is (more on this in later sections).
1919

2020
OpenAPI's provides reference capabilities using the [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03) specification.
2121

2222
### JSON Example
2323

24-
``` json
24+
``` js
2525
{
2626
// ...
2727
definitions: {

0 commit comments

Comments
 (0)