master: fix ffi documentation at the source

The branch "master" has been updated in SBCL:
       via  a797aedf9d9fbf2662f942e130b309865997d865 (commit)
      from  f832c8e48ec08902901863db5c24ddfecb842a9f (commit)

- Log -----------------------------------------------------------------
commit a797aedf9d9fbf2662f942e130b309865997d865
Author: Gabor Melis <[email protected]>
Date:   Sat Aug 15 17:50:15 2026 +0200

    fix ffi documentation at the source
    
    The generated texinfo files (e.g. ffi.texinfo) are under version
    control only to be able to conveniently track the Markdown-to-Texinfo
    output until it's deemed stable enough.
---
 doc/manual/ffi.texinfo         | 6 +++---
 src/code/target-alieneval.lisp | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/manual/ffi.texinfo b/doc/manual/ffi.texinfo
index b052c6eed..880ba90ac 100644
--- a/doc/manual/ffi.texinfo
+++ b/doc/manual/ffi.texinfo
@@ -775,9 +775,9 @@ call the function (as though it was declared with a prototype). The
 type need not be known at compile time, but only known-type calls
 are efficiently compiled.
 
-On x86-64 and ARM64 systems, structures may be passed and returned by
-value. The implementation follows the System V AMD64/Microsoft x64 and
-AAPCS64 specifications respectively.
+On x86-64 and ARM64 systems, structures may be passed and returned
+by value. The implementation follows the System V AMD64 / Microsoft
+x64 and AAPCS64 specifications, respectively.
 
 Here is an example which allocates a @code{(struct foo)}, calls a foreign
 function to initialize it, then returns a Lisp vector of all
diff --git a/src/code/target-alieneval.lisp b/src/code/target-alieneval.lisp
index 19ad54179..499b67aed 100644
--- a/src/code/target-alieneval.lisp
+++ b/src/code/target-alieneval.lisp
@@ -826,9 +826,9 @@ null byte."
   type need not be known at compile time, but only known-type calls
   are efficiently compiled.
 
-  On Unix-like x86-64 and ARM64 systems, structures may be passed and
-  returned by value. The implementation follows the System V AMD64 ABI
-  and AAPCS64 specifications respectively.
+  On x86-64 and ARM64 systems, structures may be passed and returned
+  by value. The implementation follows the System V AMD64 / Microsoft
+  x64 and AAPCS64 specifications, respectively.
 
   Here is an example which allocates a `(STRUCT FOO)`, calls a foreign
   function to initialize it, then returns a Lisp vector of all

-----------------------------------------------------------------------


hooks/post-receive
-- 
SBCL