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.

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

fixed typo #2736

Merged
merged 1 commit into from
May 18, 2024
Merged
Changes from all commits
Commits
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 docs/UsersGuide/user/port-comp-top.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ at a time by a component-wide mutex. This is also combined into the "kind" attri
![Port Image](../media/core1.png)

**Figure 1. Port connectivity.** Ports are connected to ports of the same type. When used by a *component*, the ports
can define directionality. Using *serialized ports* (see blow), serializes the call and passes it to a data buffer
can define directionality. Using *serialized ports* (see below), serializes the call and passes it to a data buffer
such that it can be sent and deserialized anywhere.

When discussing ports, one must be careful to distinguish between the port **design** and the port instantiation. A
Expand Down Expand Up @@ -224,4 +224,4 @@ topology. Alternate implementations can therefore easily be swapped, for example
## Conclusion

F´ is decomposed into a federation of discrete components organized into a system graph. The interconnections in this
graph are handled through port calls such that the otherwise independent components can interact with each other.
graph are handled through port calls such that the otherwise independent components can interact with each other.
Loading