Skip to content

Commit

Permalink
docs: fix typos (#1098)
Browse files Browse the repository at this point in the history
Signed-off-by: vuittont60 <81072379+vuittont60@users.noreply.github.com>
  • Loading branch information
vuittont60 committed Jan 9, 2024
1 parent 40e9a87 commit 5d0e4b3
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion aries/wrappers/uniffi-aries-vcx/core/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This crate contains the proof of concept UniFFI wrapper over the `aries-vcx` cra

# Scaffolding

Scaffolding is the rust code generated by UniFFI to create C-callable bindings to this crate. These bindings are automatically built by `build.rs`, targetting the `vcx.udl` file. These bindings are located in the `target` directory of the project/workspace and will show compiler errors if the `vcx.udl` interface does not integrate with this crate.
Scaffolding is the rust code generated by UniFFI to create C-callable bindings to this crate. These bindings are automatically built by `build.rs`, targeting the `vcx.udl` file. These bindings are located in the `target` directory of the project/workspace and will show compiler errors if the `vcx.udl` interface does not integrate with this crate.

# Wrapper generation

Expand Down
2 changes: 1 addition & 1 deletion misc/simple_message_relay/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Simple Message Relay
The simple message relay is a basic implementation of a mediator/relay service which can be used for testing agent-to-agent comms.

*This relay should never be used in production/public environments, as it intentionally lacks user authorization and data persistance for testing simplicitly purposes.*
*This relay should never be used in production/public environments, as it intentionally lacks user authorization and data persistence for testing simplicity purposes.*

Like a mediator, an agent can provide their HTTP/s "user endpoint" to peers during DIDComm connection protocols. An agent can then poll to collect incoming messages that have been sent to their endpoint.

Expand Down

0 comments on commit 5d0e4b3

Please sign in to comment.