From 3c0c0f5b4a1ca8382c70c70e29f9e6b4d7f0f57f Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Mon, 31 Mar 2014 10:02:15 -0700 Subject: [PATCH] Yet more edits. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1a573a1..2c1ab3c 100644 --- a/README.md +++ b/README.md @@ -482,10 +482,10 @@ JMustache is internally thread safe with the following caveats: one another, they'll simply both resolve the variable instead of one resolving the variable and the other using the cached resolution. -So the executive summary is: as long as all helper classes you supply are thread-safe, it is safe -to share a `Mustache.Compiler` instance across threads to compile templates. If you pass immutable -data to your templates when executing, it is safe to share a `Template` instance across threads, -with multiple threads executing the template simultaneously. +So the executive summary is: as long as all helper classes you supply are thread-safe (or you use +the defaults), it is safe to share a `Mustache.Compiler` instance across threads to compile +templates. If you pass immutable data to your templates when executing, it is safe to have multiple +threads simultaneously execute a single `Template` instance. Limitations ===========