From 6aea3f015ae13878adba889d855871e6d1925158 Mon Sep 17 00:00:00 2001 From: Brian Donovan Date: Fri, 5 Jan 2018 15:10:28 -0500 Subject: [PATCH] Remove apostrophe to correct grammar. (#5793) In this case we want the 3rd person present form of "let", not the contraction "let us". --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e9c6d500a3..f8f495ed04 100644 --- a/README.md +++ b/README.md @@ -111,7 +111,7 @@ Typically, you can move computations or blocking IO to some other thread via `su RxJava operators don't work with `Thread`s or `ExecutorService`s directly but with so called `Scheduler`s that abstract away sources of concurrency behind an uniform API. RxJava 2 features several standard schedulers accessible via `Schedulers` utility class. These are available on all JVM platforms but some specific platforms, such as Android, have their own typical `Scheduler`s defined: `AndroidSchedulers.mainThread()`, `SwingScheduler.instance()` or `JavaFXSchedulers.gui()`. -The `Thread.sleep(2000);` at the end is no accident. In RxJava the default `Scheduler`s run on daemon threads, which means once the Java main thread exits, they all get stopped and background computations may never happen. Sleeping for some time in this example situations let's you see the output of the flow on the console with time to spare. +The `Thread.sleep(2000);` at the end is no accident. In RxJava the default `Scheduler`s run on daemon threads, which means once the Java main thread exits, they all get stopped and background computations may never happen. Sleeping for some time in this example situations lets you see the output of the flow on the console with time to spare. Flows in RxJava are sequential in nature split into processing stages that may run **concurrently** with each other: