Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: minor typos in mbus README #1197

Merged
merged 1 commit into from
Dec 19, 2023
Merged

docs: minor typos in mbus README #1197

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions packages/binding-mbus/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The physical bus address of the unit targeted by the mbus request.

### mbus:offset

This property defines the id of the data that are meant to be read. Specifying an id of -1 will return informations about the targeted M-Bus client.
This property defines the id of the data that are meant to be read. Specifying an id of -1 will return information about the targeted M-Bus client.

### mbus:timeout

Expand Down Expand Up @@ -83,7 +83,7 @@ This implementation handles multiple requests to the same slave by combining the

## Combination

When two **requests** are made on the same unitID, then they are combined into a single **transaction**. Note that this algorithm is currently rather simple: New **requests** are just checked if they can be combined to an existing **transaction**. If not, a new **transcation** is created. When a **transcation** completes, all **requests** contained in this **transaction** are completed.
When two **requests** are made on the same unitID, then they are combined into a single **transaction**. Note that this algorithm is currently rather simple: New **requests** are just checked if they can be combined to an existing **transaction**. If not, a new **transaction** is created. When a **transaction** completes, all **requests** contained in this **transaction** are completed.

## Serialization

Expand Down
Loading