From b1e481408a2395289c8ff1266ab298489407b1fc Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Mon, 12 Feb 2018 23:01:40 +0100 Subject: [PATCH] Tweak spelling a bit in Exporting for the Web --- getting_started/workflow/export/exporting_for_web.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting_started/workflow/export/exporting_for_web.rst b/getting_started/workflow/export/exporting_for_web.rst index 4a7f59207..87c2be453 100644 --- a/getting_started/workflow/export/exporting_for_web.rst +++ b/getting_started/workflow/export/exporting_for_web.rst @@ -29,7 +29,7 @@ Using cookies for data persistence Users must **allow cookies** (specifically IndexedDB) if persistence of the ``user://`` file system is desired. When playing a game presented in an ``iframe``, **third-party** cookies must also be enabled. Incognito/private -mode also prevents persistence. +browsing mode also prevents persistence. The method ``OS.is_userfs_persistent()`` can be used to check if the ``user://`` file system is persistent, but can give false positives in some @@ -113,7 +113,7 @@ The ``.pck`` file is binary, usually delivered with the MIME-type Delivering the files with server-side compression is recommended especially for the ``.pck`` and ``.wasm`` files, which are usually large in size. The WebAssembly module compresses particularly well, down to around a quarter -of its original size with GZip. +of its original size with gzip compression. Export options --------------