From 68c8a69f4cdda9e6e1d80f1ed90efbabf410f20c Mon Sep 17 00:00:00 2001 From: George Miroshnykov Date: Thu, 21 Apr 2011 14:43:12 +0300 Subject: [PATCH] Close #962: Fixed typo in vm.runInNewContext docs. EDIT: Also added another typo fix to this commit. --isaacs --- doc/api/vm.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/vm.markdown b/doc/api/vm.markdown index 3fff4ba8b5..2b7869da49 100644 --- a/doc/api/vm.markdown +++ b/doc/api/vm.markdown @@ -33,7 +33,7 @@ Example of using `vm.runInThisContext` and `eval` to run the same code: `eval` does have access to the local scope, so `localVar` is changed. In case of syntax error in `code`, `vm.runInThisContext` emits the syntax error to stderr -and throws.an exception. +and throws an exception. ### vm.runInNewContext(code, [sandbox], [filename]) @@ -62,7 +62,7 @@ Note that running untrusted code is a tricky business requiring great care. To global variable leakage, `vm.runInNewContext` is quite useful, but safely running untrusted code requires a separate process. -In case of syntax error in `code`, `vm.runInThisContext` emits the syntax error to stderr +In case of syntax error in `code`, `vm.runInNewContext` emits the syntax error to stderr and throws an exception.