Skip to content

Commit 4cfeca3

Browse files
authored
Merge pull request #250 from asyncapi/feature/improve-spec-intro
Improve spec intro
2 parents d339448 + cf7c625 commit 4cfeca3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versions/next/asyncapi.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The AsyncAPI Specification is licensed under [The Apache License, Version 2.0](h
1212

1313
## Introduction
1414

15-
The AsyncAPI Specification is a project used to describe and document Asynchronous APIs.
15+
The AsyncAPI Specification is a project used to describe and document message-driven APIs in a machine-readable format. It’s protocol-agnostic, so you can use it for APIs that work over any messaging protocol (e.g., AMQP, MQTT, WebSockets, Kafka, STOMP, etc).
1616

1717
The AsyncAPI Specification defines a set of files required to describe such an API.
1818
These files can then be used to create utilities, such as documentation, integration and/or testing tools.
@@ -95,7 +95,7 @@ A consumer is a type of application, connected to a [message broker](#definition
9595

9696
### <a name="format"></a>Format
9797

98-
The files describing the Asynchronous API in accordance with the AsyncAPI Specification are represented as JSON objects and conform to the JSON standards.
98+
The files describing the message-driven API in accordance with the AsyncAPI Specification are represented as JSON objects and conform to the JSON standards.
9999
YAML, being a superset of JSON, can be used as well to represent a A2S (AsyncAPI Specification) file.
100100

101101
For example, if a field is said to have an array value, the JSON array representation will be used:

0 commit comments

Comments
 (0)