chore: fix spelling

John Bampton 2 years ago committed by lijunlong
parent c93ef77262
commit f39a584775

@ -142,10 +142,10 @@ $ClientP._post_by_form = function (url, content, args) {
reqId: reqId
_post_forms[reqId] = obj;
var submited = false;
var submitted = false;
// var onloadCount = 0;
obj.onload = function() {
if (!submited) return;
if (!submitted) return;
// alert('contentLoad ' + (++onloadCount) + ' times\n' + this);
@ -237,7 +237,7 @@ $ClientP._post_by_form = function (url, content, args) {
_ipt = null;
submited = true;
submitted = true;
$ = function (url) {

@ -326,7 +326,7 @@ of the string is computed with C<strlen()>.
Otherwise C<ptr> is converted to a C<"void *"> and C<len> gives the
length of the data. The data may contain embedded zeros and need not be
byte-oriented (though this may cause endianess issues).
byte-oriented (though this may cause endianness issues).
This function is mainly useful to convert (temporary) C<"const char *">
pointers returned by C functions to Lua strings and store them or pass

@ -847,7 +847,7 @@ through unions is explicitly detected and allowed.
=item * B<Constructor>: a ctype object can be called and used as a
constructor. This is equivalent to C<, ...)>, unless a
C<__new> metamethod is defined. The C<__new> metamethod is called with
the ctype object plus any other arguments passed to the contructor.
the ctype object plus any other arguments passed to the constructor.
Note that you have to use C<> inside of it, since calling
C<ct(...)> would cause infinite recursion.

@ -158,7 +158,7 @@ also the C<-b> command line option.
The generated bytecode is portable and can be loaded on any
architecture that LuaJIT supports, independent of word size or
endianess. However the bytecode compatibility versions must match.
endianness. However the bytecode compatibility versions must match.
Bytecode stays compatible for dot releases (x.y.0 E<rarr> x.y.1), but
may change with major or minor releases (2.0 E<rarr> 2.1) or between
any beta release. Foreign bytecode (e.g. from Lua 5.1) is incompatible

@ -136,7 +136,7 @@ side. But if you do, please read on.
The Win32/Win64 build of OpenResty is currently built via the MSYS2/MinGW toolchain, including
MinGW gcc 7.2.3, MSYS2 perl 5.24.4, MSYS2 bash, MSYS2 make, and etc. Basically, it is currently built via
the following cmmands:
the following commands: