unittest: Remove remaining moonscript references

2 files changed, 5 insertions, 6 deletions

diff --git a/test/unit/formatc.lua b/test/unit/formatc.lua
index dc1fb3fd9c..bafaf09310 100644
--- a/test/unit/formatc.lua
+++ b/test/unit/formatc.lua
@@ -215,7 +215,6 @@ end
 -- uncomment the following lines (and comment the return) for standalone
 -- operation (very handy for debugging)
 local function standalone(...)
-  require "moonscript"
   Preprocess = require("preprocess")
   Preprocess.add_to_include_path('./../../src')
   Preprocess.add_to_include_path('./../../build/include')
diff --git a/test/unit/garray_spec.lua b/test/unit/garray_spec.lua
index ab38176c41..c0c6d7e9ce 100644
--- a/test/unit/garray_spec.lua
+++ b/test/unit/garray_spec.lua
@@ -13,11 +13,11 @@ local NULL = helpers.NULL
 local garray = cimport('./src/nvim/garray.h')
 
 -- define a basic interface to garray. We could make it a lot nicer by
--- constructing a moonscript class wrapper around garray. It could for
--- example associate ga_clear_strings to the underlying garray cdata if the
--- garray is a string array. But for now I estimate that that kind of magic
--- might make testing less "transparant" (i.e.: the interface would become
--- quite different as to how one would use it from C.
+-- constructing a class wrapper around garray. It could for example associate
+-- ga_clear_strings to the underlying garray cdata if the garray is a string
+-- array. But for now I estimate that that kind of magic might make testing
+-- less "transparant" (i.e.: the interface would become quite different as to
+-- how one would use it from C.
 
 -- accessors
 function ga_len(garr)