Fix typos in docs
Change-Id: I71aeb8f1e5fc5f3e330e593a463858dd65e6093b
This commit is contained in:
parent
692da2b7c7
commit
d0bbfc090b
@ -223,7 +223,7 @@ There are a few options to unsubscribe registered callbacks:
|
||||
resource R, any notification of events related to resource R will no longer be handed
|
||||
over to C, after the unsubscribe_by_resource() invocation.
|
||||
* unsubscribe_all(): say that callback C has subscribed to events A, B for resource R1,
|
||||
and events C, D for resource R2, any notification of events pertaining resouces R1 and
|
||||
and events C, D for resource R2, any notification of events pertaining resources R1 and
|
||||
R2 will no longer be handed over to C, after the unsubscribe_all() invocation.
|
||||
|
||||
The snippet below shows these concepts in action:
|
||||
|
@ -391,7 +391,7 @@ will be removed. The following aspects are captured:
|
||||
effort is not considered justified. Assessment may change in the
|
||||
future.
|
||||
|
||||
Absense of an entry for an existing plugin or driver means no active effort
|
||||
Absence of an entry for an existing plugin or driver means no active effort
|
||||
has been observed or potentially not required.
|
||||
* Completed in: the release in which the effort is considered completed. Code
|
||||
completion can be deemed as such, if there is no overlap/duplication between
|
||||
|
Loading…
Reference in New Issue
Block a user