Skip to content
This repository has been archived by the owner on Jun 27, 2024. It is now read-only.

Commit

Permalink
fixed typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Giridharan002 committed Apr 4, 2024
1 parent 9ac48dc commit ac68c22
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion bots/bots-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

The above diagram illustrates the general concepts of how a Rocket.Chat server communicates with a chatbot framework or platform. These concepts are applicable to external bots.

Bots architecture consists of two main parts: Rocket.Chat host and [bot host](bots-architecture.md#bots-host). These two parts are connected with each other via Rocket.Chat SDK methods. Bot host runs externally to the Rocket.Chat host, and consists of the bot infrastructure and, typically, external [services](bots-architecture.md#external-services). The bot infrastructure in turn Worksconsists of SDK, [adapter](bots-architecture.md#framework-adapter), and [framework](bots-architecture.md#bot-framework).
Bots architecture consists of two main parts: Rocket.Chat host and [bot host](bots-architecture.md#bots-host). These two parts are connected with each other via Rocket.Chat SDK methods. Bot host runs externally to the Rocket.Chat host, and consists of the bot infrastructure and, typically, external [services](bots-architecture.md#external-services). The bot infrastructure in turn, consists of SDK, [adapter](bots-architecture.md#framework-adapter), and [framework](bots-architecture.md#bot-framework).

A bot, being subscribed to a room's messages (all or specific ones) handles these messages and responds back to the user in an interactive manner. The conversational model can be designed and managed by tooling and frameworks on the bot host.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ We've created a convenient helper script to streamline the testing and deploymen
This script is designed to be utilized using the command `yarn fuselage -a [action] -p [package]`, offering a flexible way to perform various actions. Actions are specified using the `-a | --action` flag, and the available options are: `[link|undo|unlink|next|latest|next-all|latest-all]`.

*  `link` : Creates a symbolic link for the fuselage package 
*  `undo` or `unlink` : Removes the symbolic li nk for the fuselage package 
*  `undo` or `unlink` : Removes the symbolic link for the fuselage package 
*  `next` : Update dependencies with the @next npm package version 
*  `latest` : Update dependencies with the @latest npm package version 
*  `next-all` : Update ALL fuselage dependencies with the @next npm packages version 
Expand Down
2 changes: 1 addition & 1 deletion omnichannel/whatsapp-business-template-messages.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ In this guide, we'll be creating a simple shipping reminder template message. To
* Go to your **Business Account** and navigate to **WhatsApp Manager.**
* Navigate to **Account tools > Message templates** and click **Create template**.
* Add the **category**, **name**, and **language** of the template message. 
* **Category**: Select **Utitlity** for this example guide.
* **Category**: Select **Utility** for this example guide.
* **Name**: Add a **name** for the template message.
* **Language**: Select **English** for this example guide.
* Click **Continue**.
Expand Down

0 comments on commit ac68c22

Please sign in to comment.