From 9e29b6dad21ab796dbf67d6886c198f3be7a29a0 Mon Sep 17 00:00:00 2001
From: olsonpm <olsonpm@users.noreply.github.com>
Date: Fri, 12 May 2017 23:54:01 -0500
Subject: [PATCH] clarify wording (#1931)

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 205395f0..33a9c716 100644
--- a/README.md
+++ b/README.md
@@ -410,8 +410,9 @@ to set `true`; it's effectively a shortcut for `foo=true`).
   being compressed into `1/0`, which may cause performance issues on Chrome.
 
 - `side_effects` -- default `false`. Pass `true` to potentially drop functions
-marked as "pure".  (A function is marked as "pure" via the comment annotation
-`/* @__PURE__ */` or `/* #__PURE__ */`)
+marked as "pure".  A function call is marked as "pure" if a comment annotation
+`/*@__PURE__*/` or `/*#__PURE__*/` immediately precedes the call. For example:
+`/*@__PURE__*/foo()`;
 
 
 ### The `unsafe` option
-- 
2.34.1