From 633b9b2c8964b6cce302d9a68fb1f0477e5b6e38 Mon Sep 17 00:00:00 2001 From: Nicholas Jamieson Date: Wed, 17 Jun 2020 12:07:53 +1000 Subject: [PATCH] chore: fix typos --- docs_app/content/deprecations/scheduler-argument.md | 2 +- docs_app/content/guide/higher-order-observables.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs_app/content/deprecations/scheduler-argument.md b/docs_app/content/deprecations/scheduler-argument.md index 66dbc3ef3c..6fc576dd88 100644 --- a/docs_app/content/deprecations/scheduler-argument.md +++ b/docs_app/content/deprecations/scheduler-argument.md @@ -44,7 +44,7 @@ scheduled(of([1,2,3]), asyncScheduler).subscribe(x => console.log(x)); ### Refactoring of `merge`, `concat`, `startWith` and `endWith` -In case you used to pass a scheduler argument to one of these operators you propably had code like this: +In case you used to pass a scheduler argument to one of these operators you probably had code like this: ```ts import { concat, of, asyncScheduler } from 'rxjs'; diff --git a/docs_app/content/guide/higher-order-observables.md b/docs_app/content/guide/higher-order-observables.md index d511ea46bf..9d6c053d8f 100644 --- a/docs_app/content/guide/higher-order-observables.md +++ b/docs_app/content/guide/higher-order-observables.md @@ -10,7 +10,7 @@ const fileObservable = urlObservable.pipe( `http.get()` returns an Observable for each URL. Now you have an Observable *of* Observables, a higher-order Observable. -But how do you work with a higher-order Observable? Typically, by _flattening_: by converting a higher-order Obser vable into an ordinary Observable. For example: +But how do you work with a higher-order Observable? Typically, by _flattening_: by converting a higher-order Observable into an ordinary Observable. For example: ```ts const fileObservable = urlObservable.pipe(