Misc. updates to docs.

diff --git a/doc/ext_ffi.html b/doc/ext_ffi.html
index 0bbf760669c007a2d030f865f44364659150554a..6546678e07f15c783be85472a6c5887bd4d00426 100644 (file)
--- a/doc/ext_ffi.html
+++ b/doc/ext_ffi.html
@@ -84,10 +84,10 @@ code a C compiler would generate. Calls to C functions can
 be inlined in JIT-compiled code, unlike calls to functions bound via
 the classic Lua/C API.
 </p>
-<p>
+<p><em>
 This page gives a short introduction to the usage of the FFI library.
-Please use the FFI sub-topics in the navigation bar to learn more.
-</p>
+<em>Please use the FFI sub-topics in the navigation bar to learn more.</em>
+</em></p>
 
 <h2 id="call">Motivating Example: Calling External C Functions</h2>
 <p>

diff --git a/doc/ext_ffi_semantics.html b/doc/ext_ffi_semantics.html
index b612dbc5beeb908aa7997629102f72fdd16cc48a..624f9efee9e3b93db0f97996cb56406e6c41fe10 100644 (file)
--- a/doc/ext_ffi_semantics.html
+++ b/doc/ext_ffi_semantics.html
@@ -80,7 +80,7 @@ applications using the LuaJIT FFI for developers with a C or C++
 background.
 </p>
 <p class="indent" style="color: #c00000;">
-Please note: this is the first public release of the FFI library. This
+Please note: this is an early public release of the FFI library. This
 does not comprise the final specification for the FFI semantics, yet.
 Some of the semantics may need to be changed, based on feedback from
 developers. Please <a href="contact.html">report</a> any problems you

diff --git a/doc/faq.html b/doc/faq.html
index 8de8c3f12bb525edb5f931ccac1243c3f5d1ef57..b28a72cf81a89cb8960708eac108454caa49337f 100644 (file)
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -152,9 +152,10 @@ The compiler will happily optimize away such indirections.</dd>
 <dd>Because it's a compiler &mdash; it needs to generate native
 machine code. This means the code generator must be ported to each
 architecture. And the fast interpreter is written in assembler and
-must be ported, too. This is quite an undertaking.<br> Currently only
-x86, x64 and PPC/e500v2 CPUs are supported. Other architectures will follow
-based on sufficient user demand and/or sponsoring.</dd>
+must be ported, too. This is quite an undertaking.<br>
+The <a href="install.html">install documentation</a> shows the supported
+architectures. Other architectures will follow based on sufficient user
+demand and/or sponsoring.</dd>
 </dl>
 
 <dl>

diff --git a/doc/install.html b/doc/install.html
index f6c99c17bddd1530845161f955d42fe03bea4d01..7341fd0776c9141971cf3af5e6ac6ea91c1a2d68 100644 (file)
--- a/doc/install.html
+++ b/doc/install.html
@@ -484,7 +484,8 @@ overridden, but it's <em>not</em> recommended, except for special needs
 like cross-builds:
 <tt>BUILDMODE, CC, HOST_CC, STATIC_CC, DYNAMIC_CC, CFLAGS, HOST_CFLAGS,
 TARGET_CFLAGS, LDFLAGS, HOST_LDFLAGS, TARGET_LDFLAGS, TARGET_SHLDFLAGS,
-LIBS, HOST_LIBS, TARGET_LIBS, CROSS, HOST_SYS, TARGET_SYS</tt></li>
+TARGET_FLAGS, LIBS, HOST_LIBS, TARGET_LIBS, CROSS, HOST_SYS, TARGET_SYS
+</tt></li>
 </ul>
 <p>
 The build system has a special target for an amalgamated build, i.e.

diff --git a/doc/luajit.html b/doc/luajit.html
index 5f01eaf4ed44ff36cad154988d534d537d20de44..7916b6c9ae20b89063c8fe2c4126631e7022a354 100644 (file)
--- a/doc/luajit.html
+++ b/doc/luajit.html
@@ -79,8 +79,8 @@ standard Lua interpreter and can be deployed as a drop-in replacement.
 <p>
 LuaJIT offers more performance, at the expense of portability. It
 currently runs on all popular operating systems based on
-<b>x86</b> or <b>x64 CPUs</b> (Linux, Windows, OSX etc.) or embedded Linux
-systems based on <b>PPC/e500v2 CPUs</b>.
+<b>x86</b> or <b>x64</b> CPUs (Linux, Windows, OSX etc.) or embedded
+systems based on <b>ARM</b> (Android, iOS) or <b>PPC/e500v2</b> CPUs.
 Other platforms will be supported in the future, based on user demand
 and sponsoring.
 </p>