URL correction

zephir-lang · Jan 3, 2019 · e85e2f7 · e85e2f7
1 parent 91e4a8f
commit e85e2f7
Show file tree

Hide file tree

Showing 23 changed files with 60 additions and 60 deletions.
diff --git a/el-GR/config.md b/el-GR/config.md
@@ -180,7 +180,7 @@ Extension description - any text describing your extension:
 
 <a name='destructors'></a>
 ## destructors
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
 ```json
 {
@@ -306,7 +306,7 @@ Any additional files you want to add to the compilation process - the search dir
 
 <a name='globals'></a>
 ## globals
-Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information.
+Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information.
 
 ```json
 {
@@ -325,7 +325,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 <a name='info'></a>
 ## info
-`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information.
+`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information.
 
 ```json
 {
@@ -343,7 +343,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 <a name='initializers'></a>
 ## initializers
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
 ```json
 {

diff --git a/el-GR/lifecycle.md b/el-GR/lifecycle.md
@@ -18,7 +18,7 @@ Consider the following diagram:
 
 ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png)
 
-Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings.
+Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings.
 
 Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here.
 
@@ -103,4 +103,4 @@ The `destructors` block looks something like this:
 }
 ```
 
-Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space.
+Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space.
diff --git a/el-GR/optimizers.md b/el-GR/optimizers.md
@@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the
     }
 
 
-This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file:
+This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file:
 
     "extra-sources": [
         "utils/pi.c"
@@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th
     ]
 
 
-Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers)
+Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers)
diff --git a/el-GR/tutorial.md b/el-GR/tutorial.md
@@ -78,7 +78,7 @@ If everything is well, you should see the following help (or something very simi
         -W([a-z0-9\-]+)     Turns a warning off
 
 
-If something went wrong, please return back to the [installation](/[[language]]/[[version]]/installation) page.
+If something went wrong, please return back to the [installation](/{{ page.version }}/{{ page.language }}/installation) page.
 
 <a name='extension-skeleton'></a>
 
@@ -278,4 +278,4 @@ In the following screencast you can watch how to create the extension explained
 
 ## Conclusion
 
-This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir!
+This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir!
diff --git a/en/config.md b/en/config.md
@@ -180,7 +180,7 @@ Extension description - any text describing your extension:
 
 <a name='destructors'></a>
 ## destructors
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
 ```json
 {
@@ -306,7 +306,7 @@ Any additional files you want to add to the compilation process - the search dir
 
 <a name='globals'></a>
 ## globals
-Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information.
+Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information.
 
 ```json
 {
@@ -325,7 +325,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 <a name='info'></a>
 ## info
-`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information.
+`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information.
 
 ```json
 {
@@ -343,7 +343,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 <a name='initializers'></a>
 ## initializers
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
 ```json
 {

diff --git a/en/lifecycle.md b/en/lifecycle.md
@@ -17,7 +17,7 @@ Consider the following diagram:
 
 ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png)
 
-Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings.
+Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings.
 
 Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is **_strongly_** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here.
 

diff --git a/en/optimizers.md b/en/optimizers.md
@@ -175,7 +175,7 @@ double my_calculate_pi(zval *accuracy) {
 }
 ```
 
-This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file:
+This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file:
 
 ```json
 "extra-sources": [

diff --git a/es-ES/config.md b/es-ES/config.md
@@ -187,7 +187,7 @@ Extension description - any text describing your extension:
 
 ## destructores
 
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
     {
         "destructors": [
@@ -321,7 +321,7 @@ Any additional files you want to add to the compilation process - the search dir
 
 ## globals
 
-Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information.
+Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information.
 
     {
         "globals": {
@@ -341,7 +341,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 ## info
 
-`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information.
+`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information.
 
     {
         "info": [
@@ -360,7 +360,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa
 
 ## iniciadores
 
-This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information.
+This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information.
 
     {
         "initializers": [
@@ -549,4 +549,4 @@ Compiler warnings which should be enabled or disabled in the current project:
             "nonexistent-function": true,
             "nonexistent-class": true
         }
-    }
+    }
diff --git a/es-ES/lifecycle.md b/es-ES/lifecycle.md
@@ -18,7 +18,7 @@ Consider the following diagram:
 
 ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png)
 
-Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings.
+Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings.
 
 Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here.
 
@@ -103,4 +103,4 @@ The `destructors` block looks something like this:
 }
 ```
 
-Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space.
+Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space.
diff --git a/es-ES/optimizers.md b/es-ES/optimizers.md
@@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the
     }
 
 
-This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file:
+This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file:
 
     "extra-sources": [
         "utils/pi.c"
@@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th
     ]
 
 
-Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers)
+Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers)
diff --git a/es-ES/tutorial.md b/es-ES/tutorial.md
@@ -75,7 +75,7 @@ Si todo está bien, debería ver la siguiente ayuda (o algo muy similar):
         -W([a-z0-9\-]+)     Apaga una advertencia
 
 
-Si algo salió mal, por favor regrese a la [página de instalación](/[[language]]/[[version]]/installation).
+Si algo salió mal, por favor regrese a la [página de instalación](/{{ page.version }}/{{ page.language }}/installation).
 
 <a name='extension-skeleton'></a>
 
@@ -274,4 +274,4 @@ En el siguiente video tutorial puedes ver como crear la extensión explicada en
 
 ## Conclusión
 
-Este es un tutorial muy simple y como se puede ver, es fácil empezar a construir una extensión usando Zephir. Te invitamos a seguir leyendo el manual para que puedas descubrir algunas funciones adicionales que ofrece Zephir!
+Este es un tutorial muy simple y como se puede ver, es fácil empezar a construir una extensión usando Zephir. Te invitamos a seguir leyendo el manual para que puedas descubrir algunas funciones adicionales que ofrece Zephir!