diff --git a/docs/contributing.md b/docs/contributing.md index a99f5f25..cf71e632 100644 --- a/docs/contributing.md +++ b/docs/contributing.md @@ -17,9 +17,9 @@ incomplete list of starting points for contributions: created. * The [issues page](https://github.com/bemanproject/execution/issues) lists known issues. -* The implememtation of a component may be missing. +* The implementation of a component may be missing. * The layout of some pages related to the project can be improved. -* Some behaviour of a component isn't tested or documented. +* Some behavior of a component isn't tested or documented. * You found something which should be linked from the [resources](https://github.com/bemanproject/execution/blob/main/docs/resources.md) page. * There are [pull requests](https://github.com/bemanproject/execution/pulls) diff --git a/docs/intro-examples.md b/docs/intro-examples.md index 23487793..0ab96501 100644 --- a/docs/intro-examples.md +++ b/docs/intro-examples.md @@ -17,7 +17,7 @@ synchronously produce the result. The intention is to show a basic use of some involved components to build up a feeling of how things work. -The componentes for `std::execution` are declared in the header +The components for `std::execution` are declared in the header ``. This particular implementation implements the cmponents in namespace `beman::execution` declared in the header ``: diff --git a/docs/overview.md b/docs/overview.md index 363b831a..b2c83f10 100644 --- a/docs/overview.md +++ b/docs/overview.md @@ -409,7 +409,7 @@ struct custom_t: forwarding_query_t { get_env(queryable) -> env **Default**: `empty_env`
-The expresion get_env(queryable) is used to get the environment env associated with queryable. To provide a non-default environment for a queryable a `get_env` member needs to be defined. If queryable doesn’t provide the get_env query an object of type empty_env is returned. +The expression get_env(queryable) is used to get the environment env associated with queryable. To provide a non-default environment for a queryable a `get_env` member needs to be defined. If queryable doesn’t provide the get_env query an object of type empty_env is returned. The value of the expression is
  1. the result of as_const(queryable).get_env() if this expression is valid and noexcept.
  2. empty_env otherwise. @@ -560,7 +560,7 @@ Otherwise the value is never_stop_token{}.
    connect(sender, receiver) -> operation_state -The expresion connect(sender, receiver) combines sender and receiver into an operation state state. When this state gets started using start(state) the operation represented by sender gets started and reports its completion to receiver or an object copied or moved from receiver. While the operation state state isn’t started it can be destroyed but once it got started it needs to stay valid until one of the completion signals is called on receiver. +The expression connect(sender, receiver) combines sender and receiver into an operation state state. When this state gets started using start(state) the operation represented by sender gets started and reports its completion to receiver or an object copied or moved from receiver. While the operation state state isn’t started it can be destroyed but once it got started it needs to stay valid until one of the completion signals is called on receiver.
    set_error(receiver, error) noexcept -> void @@ -655,7 +655,7 @@ The expression continues_on(sender, scheduler) create
    into_variant(sender) -> sender-of<set_value_t(std::variant<Tuple...>)> -The expression into_variant(sender) creates a sender which transforms the results of possibly multiple set_value completions of sender into one set_value completion respresenting the different upstream results as different options of a variant<Tuple...> where each Tuple is a tuple of values initialized with the respective arguments passed to set_value. The order of options in the variant isn’t specified. +The expression into_variant(sender) creates a sender which transforms the results of possibly multiple set_value completions of sender into one set_value completion representing the different upstream results as different options of a variant<Tuple...> where each Tuple is a tuple of values initialized with the respective arguments passed to set_value. The order of options in the variant isn’t specified.
    let_error(upstream, fun) -> sender