diff --git a/pages/en/lb3/Using-current-context.md b/pages/en/lb3/Using-current-context.md
index 8f9eec214..561fa69ac 100644
--- a/pages/en/lb3/Using-current-context.md
+++ b/pages/en/lb3/Using-current-context.md
@@ -38,11 +38,11 @@ implementation of continuation-local-storage available for Node.js,
 explicitly pass any additional context via `options` parameter
 of (remote) methods.
 
-All built-in methods like
+Built-in methods such as
 [PersistedModel.find](http://apidocs.strongloop.com/loopback/#persistedmodel-find)
 or
 [PersistedModel.create](http://apidocs.strongloop.com/loopback/#persistedmodel-create)
-were already modified to accept an optional `options` argument.
+accept an `options` argument.
 
 [Operation hooks](Operation-hooks.html) expose the `options` argument
 as `context.options`.
@@ -126,10 +126,9 @@ MyModel.beforeRemote('saveOptions', function(ctx, unused, next) {
 
 Again, a hook like this can be reused by placing the code in a mixin.
 
-Note that remote hooks are executed in order controlled by LoopBack framework, which
-may be different from the order in which you need to modify the options
-parameter and then read the modified values. Please use the next suggestion if
-this order matters in your application.
+It may not always be possible to control the order in which remote hooks are
+executed. If you need to control the order, then use a custom
+strong-remoting phase as described in the following section.
 
 ### Use a custom strong-remoting phase