# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1638793151 -3600
# Node ID 23271902921a1ca998e256e39a8e581b834c3bb0
# Parent  e22c1284ea0e0e26c41e0ba178f66763fb04cb22
replace ABI by more adequate FFI

diff -r e22c1284ea0e -r 23271902921a Sphinx/source/developers/creating-plugins.rst
--- a/Sphinx/source/developers/creating-plugins.rst	Mon Dec 06 13:13:31 2021 +0100
+++ b/Sphinx/source/developers/creating-plugins.rst	Mon Dec 06 13:19:11 2021 +0100
@@ -18,8 +18,10 @@
 <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.9.7/OrthancServer/Plugins/Include/orthanc/OrthancCPlugin.h>`__.
 As a consequence, an Orthanc plugin will typically be written using C
 or C++, although it is also possible to create native plugins using
-languages that feature compatibility with C headers and with C ABI
-(such as Rust or Objective-C).
+languages that feature compatibility with C headers and with `FFI of
+the C language
+<https://en.wikipedia.org/wiki/Foreign_function_interface>`__ (such as
+Rust or Objective-C).
 
 For developers who are more familiar with Python, it is also possible
 to create plugins using this simpler language. Check out the
@@ -67,7 +69,7 @@
 
 A plugin takes the form of a shared library (``.DLL`` under Windows,
 ``.so`` under GNU/Linux, ``.dylib`` under Apple OS X...) that uses the
-`ABI of the C language
+`FFI of the C language
 <https://en.wikipedia.org/wiki/Application_binary_interface>`__ to
 declare 4 public functions/symbols: