style(emscripten): it is called emterpreter not empterpreter

rodneyrehm · rodneyrehm · commit dd37c4e63fd7 · 2018-02-06T13:41:56.000+01:00
diff --git a/libsass/Makefile.patch b/libsass/Makefile.patch
@@ -13,7 +13,7 @@
 +		-s ALLOW_MEMORY_GROWTH=1 \
 +		-s EMTERPRETIFY=1 \
 +		-s EMTERPRETIFY_ASYNC=1 \
-+		-s EMTERPRETIFY_WHITELIST=@../empterpreter_whitelist.json \
++		-s EMTERPRETIFY_WHITELIST=@../emterpreter_whitelist.json \
 +		--memory-init-file 0
 +
 +js-debug: static
@@ -25,7 +25,7 @@
 +		-s ALLOW_MEMORY_GROWTH=1 \
 +		-s EMTERPRETIFY=1 \
 +		-s EMTERPRETIFY_ASYNC=1 \
-+		-s EMTERPRETIFY_WHITELIST=@../empterpreter_whitelist.json \
++		-s EMTERPRETIFY_WHITELIST=@../emterpreter_whitelist.json \
 +		-s ASSERTIONS=1 \
 +		-s SAFE_HEAP=1 \
 +		-s DEMANGLE_SUPPORT=1 \
diff --git a/libsass/emscripten_wrapper.cpp b/libsass/emscripten_wrapper.cpp
@@ -81,7 +81,7 @@ void sass_compile_emscripten(
   }
 
   // returning data to JS via callback rather than regular function return value and C pointer fun,
-  // because emscripten does not inform JavaScript when an (empterpreter) async function is done.
+  // because emscripten does not inform JavaScript when an (emterpreter) async function is done.
   // Since (char *) is a pointer (int) we can abuse EM_ASM_INT() to pass that back to JavaScript.
   // NOTE: Because we're performing tasks *after* we informed the JavaScript of success/error,
   // we need to make sure that those callbacks don't mess with the stack or prematurely
diff --git a/libsass/emterpreter_whitelist.json b/libsass/emterpreter_whitelist.json

Original file line number	Diff line number	Diff line change
`@@ -81,7 +81,7 @@ void sass_compile_emscripten(`
`81`	`81`	`}`
`82`	`82`
`83`	`83`	`// returning data to JS via callback rather than regular function return value and C pointer fun,`
`84`		`- // because emscripten does not inform JavaScript when an (empterpreter) async function is done.`
	`84`	`+ // because emscripten does not inform JavaScript when an (emterpreter) async function is done.`
`85`	`85`	`// Since (char *) is a pointer (int) we can abuse EM_ASM_INT() to pass that back to JavaScript.`
`86`	`86`	`// NOTE: Because we're performing tasks after we informed the JavaScript of success/error,`
`87`	`87`	`// we need to make sure that those callbacks don't mess with the stack or prematurely`