Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Commit

Permalink
Documentation - minor issue fixes (#3462)
Browse files Browse the repository at this point in the history
Fixed spelling in documentation files.
  • Loading branch information
ropereraLK authored Jan 26, 2023
1 parent b88c27d commit 719677d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/docs/reference-docs/event-task.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ sidebar_position: 4

### Introduction
EVENT is a task used to publish an event into one of the supported eventing systems in Conductor.
Conductor supports the the following eventing models:
Conductor supports the following eventing models:

1. Conductor internal events (type: conductor)
2. SQS (type: sqs)
Expand All @@ -29,7 +29,7 @@ Consider an example where we want to publish an event into SQS to notify an exte
}
```

An example where we want to publish a messase to conductor's internal queuing system.
An example where we want to publish a message to conductor's internal queuing system.
```json
{
"type": "EVENT",
Expand All @@ -56,7 +56,7 @@ An example where we want to publish a messase to conductor's internal queuing sy
* ```true``` to keep it IN_PROGRESS, wait for an external event (via Conductor or SQS or EventHandler) to complete it.

#### Output Configuration
Tasks's output are sent as a payload to the external event. In case of SQS the task's output is sent to the SQS message a a payload.
Tasks's output are sent as a payload to the external event. In case of SQS the task's output is sent to the SQS message a payload.


| name | type | description |
Expand Down

0 comments on commit 719677d

Please sign in to comment.