diff options
author | Paul Vinciguerra <pvinci@vinciconsulting.com> | 2019-10-27 17:28:10 -0400 |
---|---|---|
committer | Dave Barach <openvpp@barachs.net> | 2019-10-28 13:51:13 +0000 |
commit | 7fa3dd2881be537ec6144850064ad1419dc12f3e (patch) | |
tree | 7fa013d6e23f16f73b0ca97628c1374a009b49bd /docs/gettingstarted/developers/binary_api_support.rst | |
parent | 3b5e222f8a4d0ccd4ec4eace2551491f13de85d9 (diff) |
docs: cleanup typos on readthrough
Type: style
Change-Id: I3b15035ea6c13cd1ca3cdc9dfa9b10a6e1be9880
Signed-off-by: Paul Vinciguerra <pvinci@vinciconsulting.com>
Diffstat (limited to 'docs/gettingstarted/developers/binary_api_support.rst')
-rw-r--r-- | docs/gettingstarted/developers/binary_api_support.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/gettingstarted/developers/binary_api_support.rst b/docs/gettingstarted/developers/binary_api_support.rst index 9c17a734e44..732ce978daa 100644 --- a/docs/gettingstarted/developers/binary_api_support.rst +++ b/docs/gettingstarted/developers/binary_api_support.rst @@ -93,7 +93,7 @@ implement a variety of features: * Barrier synchronization of worker threads across thread-unsafe message handlers. Correctly-coded message handlers know nothing about the transport used -to deliver messages to/from VPP. It's reasonably straighforward to use +to deliver messages to/from VPP. It's reasonably straightforward to use multiple API message transport types simultaneously. For historical reasons, binary api messages are (putatively) sent in |