fixes, links

Author: Julien Pauli

Book/php7/build_system/building_extensions.rst

@@ -15,7 +15,7 @@ shared objects can be created by explicitly passing ``--enable-EXTNAME=shared``
 ``./configure``.
 
 While static extensions will always be available, shared extensions need to be loaded using the ``extension`` or
-``zend_extension`` ini options [#]_. Both options take either an absolute path to the ``.so`` file or a path relative to
+``zend_extension`` ini options. Both options take either an absolute path to the ``.so`` file or a path relative to
 the ``extension_dir`` setting.
 
 As an example, consider a PHP build compiled using this configure line::
@@ -33,7 +33,7 @@ directory. You can load both either by changing the ``extension_dir`` or by pass
     ~/php-src> sapi/cli/php -dextension_dir=`pwd`/modules \
                             -dzend_extension=opcache.so -dextension=gmp.so
 
-During the ``make install`` step both ``.so`` files will be moved into the extension directory of your PHP installation,
+During the ``make install`` step, both ``.so`` files will be moved into the extension directory of your PHP installation,
 which you may find using the ``php-config --extension-dir`` command. For the above build options it will be
 ``/home/myuser/myphp/lib/php/extensions/no-debug-non-zts-MODULE_API``. This value will also be the default of the
 ``extension_dir`` ini option, so you won't have to specify it explicitly and can load the extensions directly::
@@ -49,9 +49,8 @@ As a rule of thumb, you'll use static linkage for the extensions bundled by PHP
 everything else. The reason is simply that building external extensions as shared objects is easier (or at least less
 intrusive), as you will see in a moment. Another benefit is that you can update the extension without rebuilding PHP.
 
-.. [#] We'll explain the difference between a "normal" extension and a Zend extension later in the book. For now it
-       suffices to know that Zend extensions are more "low level" (e.g. opcache or xdebug) and hook into the workings of
-       the Zend Engine itself.
+.. note:: If you need informations about the difference between extensions and Zend extensions, you :doc:`may have a 
+          look at the dedicated chapter <../extensions_design/zend_extensions>`.
 
 Installing extensions from PECL
 -------------------------------
@@ -358,7 +357,7 @@ We authors, use something like this in extensions of ours::
     
 See?
 
-Or, simpler (so better) is to use PHP_VERSION_ID which you are probably much more familiar about::
+Or, simpler (so better) is to use ``PHP_VERSION_ID`` which you are probably much more familiar about::
     
     #if PHP_VERSION_ID >= 50600
     

Book/php7/build_system/building_php.rst

@@ -142,7 +142,7 @@ configuration header file ``main/php_config.h``.
 
 Both utilities produce their results from the ``configure.in`` file (which specifies most of the PHP build process),
 the ``acinclude.m4`` file (which specifies a large number of PHP-specific M4 macros) and the ``config.m4`` files of
-individual extensions and SAPIs (as well as a bunch of other ``m4`` files).
+individual extensions and SAPIs (as well as a bunch of other `m4 files <http://www.gnu.org/software/m4/m4.html>`_).
 
 The good news is that writing extensions or even doing core modifications will not require much interaction with the
 build system. You will have to write small ``config.m4`` files later on, but those usually just use two or three of the
@@ -211,8 +211,8 @@ your PHP binary contains using the ``-m`` option. For a default PHP 7.0 build th
     xmlreader
     xmlwriter
 
-If you now wanted to stop compiling the CGI SAPI, as well as the tokenizer and sqlite3 extensions and instead enable
-opcache and gmp, the corresponding configure command would be::
+If you now wanted to stop compiling the CGI SAPI, as well as the *tokenizer* and *sqlite3* extensions and instead enable
+*opcache* and *gmp*, the corresponding configure command would be::
 
     ~/php-src> ./configure --disable-cgi --disable-tokenizer --without-sqlite3 \
                            --enable-opcache --with-gmp
@@ -254,14 +254,15 @@ structures, will be reported.
 
 ``--enable-maintainer-zts`` enables thread-safety. This switch will define the ``ZTS`` macro, which in turn will enable
 the whole TSRM (thread-safe resource manager) machinery used by PHP. Writing thread-safe extensions for PHP is very
-simple, but only if make sure to enable this switch.
+simple, but only if make sure to enable this switch. If you need more information about thread safety and global 
+memory management in PHP, you should read :doc:`the globals management chapter <../extensions_design/globals_management>`
 
 On the other hand you should not use either of these options if you want to perform performance benchmarks for your
 code, as both can cause significant and asymmetrical slowdowns.
 
 Note that ``--enable-debug`` and ``--enable-maintainer-zts`` change the ABI of the PHP binary, e.g. by adding additional
-arguments to many functions. As such shared extensions compiled in debug mode will not be compatible with a PHP binary
-built in release mode. Similarly a thread-safe extension is not compatible with a thread-unsafe PHP build.
+arguments to many functions. As such, shared extensions compiled in debug mode will not be compatible with a PHP binary
+built in release mode. Similarly a thread-safe extension (ZTS) is not compatible with a non-thread-safe PHP build (NTS).
 
 Due to the ABI incompatibility ``make install`` (and PECL install) will put shared extensions in different directories
 depending on these options:
@@ -472,7 +473,7 @@ be::
     ~/php-src> make test TESTS="Zend/ ext/reflection/ ext/standard/tests/array/"
 
 We will take a more detailed look at the ``run-tests.php`` system later, in particular also talk about how to write your
-own tests and how to debug test failures.
+own tests and how to debug test failures. :doc:`See the dedicated tests chapter <../../tests/introduction>`.
 
 Fixing compilation problems and ``make clean``
 ----------------------------------------------

Book/php7/introduction.rst

@@ -1,8 +1,8 @@
 Introduction
 ============
 
-This book is a collaborative effort between several PHP developers to better document and describe how PHP works
-internally.
+This book is a collaborative effort between several developers of the PHP language to better document and describe how 
+PHP works internally.
 
 There are three primary goals of this book:
 
@@ -37,10 +37,8 @@ make it translate to efficient CPU instructions so that you can design strong/fa
 * Hackers Delight
 * Write Great Code (2 Volumes)
 
-.. note:: This book is Work-In-Progress and some chapters have not been written yet (in particular the ones on creating 
-   basic extensions and declaring functions), so if you're completely new to PHP extension development you'll have to 
-   wait until the remaining introductory chapters are published or start off with other
-   `resources on the topic <https://wiki.php.net/internals/references>`_.
+.. note:: This book is Work-In-Progress and some chapters have not been written yet. We d'ont pay attention to a 
+          specific order, but add content as we feel.
 
 The repository for this book is available on GitHub_. Please report issues and provide feedback on the `issue tracker`_.