From 1672fbbfe8873e3ed7b830b1cb274f1e7bf4d096 Mon Sep 17 00:00:00 2001 From: Robin Braun Date: Thu, 16 Apr 2020 11:52:28 +0200 Subject: [PATCH] typos --- docs/content/en/docs/Advanced Features/isolates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/en/docs/Advanced Features/isolates.md b/docs/content/en/docs/Advanced Features/isolates.md index 300b3c4f..6d597427 100644 --- a/docs/content/en/docs/Advanced Features/isolates.md +++ b/docs/content/en/docs/Advanced Features/isolates.md @@ -139,7 +139,7 @@ a setup where you have three or more threads: - A foreground isolate, probably for Flutter - Another background isolate, which could be used for networking. -You can the read data from the foreground isolate or start query streams, similar to the example +You can then read data from the foreground isolate or start query streams, similar to the example above. The background isolate would _also_ call `MoorIsolate.connect` and create its own instance of the generated database class. Writes to one database will be visible to the other isolate and also update query streams. @@ -153,7 +153,7 @@ All moor features are supported on background isolates and work out of the box. - Batched updates and inserts - Custom statements or those generated from an sql api -Please note that, will using a background isolate can reduce lag on the UI thread, the overall +Please note that, while using a background isolate can reduce lag on the UI thread, the overall database is going to be slower! There's a overhead involved in sending data between isolates, and that's exactly what moor has to do internally. If you're not running into dropped frames because of moor, using a background isolate is probably not necessary for your app.