Commit 1a04c547 authored by Oksana Zhuravlova's avatar Oksana Zhuravlova Committed by Commit Bot

Fix some typos

Change-Id: I97dd67db41337f69cc9ed54eb743b7f1664301f3
Reviewed-on: https://chromium-review.googlesource.com/1137271Reviewed-by: default avatarKen Rockot <rockot@chromium.org>
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575107}
parent a820e9f1
...@@ -167,7 +167,7 @@ interface PngDecoder { ...@@ -167,7 +167,7 @@ interface PngDecoder {
``` ```
and you'll also want to define the implementation within and you'll also want to define the implementation within
`//services/data_decoder`, pluging in some appropriate binder so the service `//services/data_decoder`, plugging in some appropriate binder so the service
knows how to bind incoming interface requests to your implementation: knows how to bind incoming interface requests to your implementation:
``` cpp ``` cpp
...@@ -687,7 +687,7 @@ if such a use case is blocking your work. ...@@ -687,7 +687,7 @@ if such a use case is blocking your work.
### Using Legacy IPC Traits ### Using Legacy IPC Traits
InsSome circumstances there may be a C++ enum, struct, or class that you want In some circumstances there may be a C++ enum, struct, or class that you want
to use in a Mojom via [type mapping](/mojo/public/cpp/bindings#Type-Mapping), to use in a Mojom via [type mapping](/mojo/public/cpp/bindings#Type-Mapping),
and that type may already have `IPC::ParamTraits` defined (possibly via and that type may already have `IPC::ParamTraits` defined (possibly via
`IPC_STRUCT_TRAITS*` macros) for legacy IPC. `IPC_STRUCT_TRAITS*` macros) for legacy IPC.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment