From 86b9c06c74261eb465f91c477f630b5ad9529d46 Mon Sep 17 00:00:00 2001 From: Tobrun Date: Mon, 17 Jun 2019 12:16:19 +0200 Subject: [node] - fix README type, granualar to granular (#14933) --- platform/node/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform/node/README.md b/platform/node/README.md index ac5bcd7e8d..7273c0813a 100644 --- a/platform/node/README.md +++ b/platform/node/README.md @@ -82,7 +82,7 @@ The first argument passed to `map.render` is an options object, all keys are opt } ``` -When you are finished using a map object, you can call `map.release()` to permanently dispose the internal map resources. This is not necessary, but can be helpful to optimize resource usage (memory, file sockets) on a more granualar level than V8's garbage collector. Calling `map.release()` will prevent a map object from being used for any further render calls, but can be safely called as soon as the `map.render()` callback returns, as the returned pixel buffer will always be retained for the scope of the callback. +When you are finished using a map object, you can call `map.release()` to permanently dispose the internal map resources. This is not necessary, but can be helpful to optimize resource usage (memory, file sockets) on a more granular level than V8's garbage collector. Calling `map.release()` will prevent a map object from being used for any further render calls, but can be safely called as soon as the `map.render()` callback returns, as the returned pixel buffer will always be retained for the scope of the callback. ## Implementing a file source -- cgit v1.2.1