Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update glossary-and-semantics.md #6363

Merged
merged 1 commit into from May 5, 2021
Merged

Update glossary-and-semantics.md #6363

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs_app/content/guide/glossary-and-semantics.md
View file
Open in desktop
Expand Up @@ -6,7 +6,7 @@ While not all of the documentation for RxJS reflects this terminology, it is a g

## Major Entities

There are high level entities that are frequently discussed. It's important to define them seperately from other lower-level concepts, because they relate to the nature of observable.
There are high level entities that are frequently discussed. It's important to define them separately from other lower-level concepts, because they relate to the nature of observable.

### Consumer

Expand All @@ -18,7 +18,7 @@ Any system or thing that is the source of values that are being pushed out of th

### Subscription

A contract where a [consumer](#Consumer) is [observing](#Observation) values pushed by a [producer](#Producer). The subscription (not to be confused with the `Subscription` class or type), is an ongoing process that amounts to the function of the observable from the Consumer's perspective. Subcription starts the moment a [subscribe](#Subscribe) action is initiated, even before the [subscribe](#Subscribe) action is finished.
A contract where a [consumer](#Consumer) is [observing](#Observation) values pushed by a [producer](#Producer). The subscription (not to be confused with the `Subscription` class or type), is an ongoing process that amounts to the function of the observable from the Consumer's perspective. Subscription starts the moment a [subscribe](#Subscribe) action is initiated, even before the [subscribe](#Subscribe) action is finished.

### Observable

Expand All @@ -42,15 +42,15 @@ The act of cleaning up resources used by a producer. This is guaranteed to happe

### Unsubscription

The act of a [consumer](#Consumer) telling a [producer](#Producer) is is no longer interested in recieving values. Causes [Teardown](#Teardown)
The act of a [consumer](#Consumer) telling a [producer](#Producer) is is no longer interested in receiving values. Causes [Teardown](#Teardown)

### Observation

A [consumer](#Consumer) reacting to [next](#Next), [error](#Error), or [complete](#Complete) [notifications](#Notification). This can only happen _during_ [subscription](#Subscription).

### Observation Chain

When an [observable](#Observable) uses another [observable](#Observable) as a [producer](#Producer), an "observation chain" is set up. That is a chain of [observation](#Observation) such that multiple [observers](#Observer) are [notifying](#Notifcation) each other in a unidirectional way toward the final [consumer](#Consumer).
When an [observable](#Observable) uses another [observable](#Observable) as a [producer](#Producer), an "observation chain" is set up. That is a chain of [observation](#Observation) such that multiple [observers](#Observer) are [notifying](#Notification) each other in a unidirectional way toward the final [consumer](#Consumer).

### Next

Expand Down Expand Up @@ -146,4 +146,4 @@ An "unhandled error" is any [error](#Error) that is not handled by a [consumer](

### Upstream And Downstream

The order in which [notifications](#Notification) are processed by [operations](#Operation) in a [stream](#Stream) have a directionality to them. "Upstream" refers to an [operation](#Operation) that was already processed before the current [operation](#Operation), and "downstream" refers to an [operation](#Operation) that _will_ be processed _after_ the current [operation](#Operation). See also: [Streaming](#Stream).
The order in which [notifications](#Notification) are processed by [operations](#Operation) in a [stream](#Stream) have a directionality to them. "Upstream" refers to an [operation](#Operation) that was already processed before the current [operation](#Operation), and "downstream" refers to an [operation](#Operation) that _will_ be processed _after_ the current [operation](#Operation). See also: [Streaming](#Stream).