Adjust internal URLs to the parsing engine

tutorial/builds.md

@@ -21,7 +21,7 @@ The CHM version of the manual is built on a Windows machine and pulled on Friday
 for distribution to mirrors. [Richard][rquadling] maintains these builds.
 
 ## Validation
-Aside from running `php configure.php –with-lang=foo` (see [editing](editing.md))
+Aside from running `php configure.php –with-lang=foo` (see [editing](editing.php))
 for a language, another way to check if the docs validated is by looking at build
 dates on the doc server. See "Doc server builds", above.
 

tutorial/editing.md

@@ -3,7 +3,7 @@
 ## Introduction
 When editing or translating the manual, you have to remember some things:
 - use only UTF-8 encoding
-- follow the project's [style guidelines](style.md)
+- follow the project's [style guidelines](style.php)
 
 ## Editing existing documentation
 Simply open the files and edit them.
@@ -26,10 +26,10 @@ cp /phpdoc/RFC/skeletons/function.xml functions/functionname.xml #for new functi
 Note: *classname*, *methodname* and *functionname* are lowercased names of the
 class, method, or function, respectively, not a literal file name.
 
-Remember the extension folder [structure](structure.md) when copying those files.
+Remember the extension folder [structure](structure.php) when copying those files.
 
 ## Translating documentation
-The translation process is described in the [translating chapter](translating.md).
+The translation process is described in the [translating chapter](translating.php).
 
 ## Validating your changes
 Every time you make changes to documentation sources (both English or translation),
@@ -54,9 +54,9 @@ there is a special mirror at [docs.php.net][docs] - where the manual is updated
 from sources every six hours. If any errors occured, a message will be delivered
 to the appropriate mailinglist (`doc-{LANG}@lists.php.net`).
 
-Read more about manual builds in the [builds appendix](builds.md).
+Read more about manual builds in the [builds appendix](builds.php).
 
-The next chapter contains [style guidelines](style.md) that you are obliged to
+The next chapter contains [style guidelines](style.php) that you are obliged to
 follow. Read them carefully.
 
 [docgen]: http://svn.php.net/viewvc/phpdoc/doc-base/trunk/scripts/docgen/

tutorial/intro.md

@@ -18,15 +18,15 @@ This guide uses some terminology that you have to know. Don't worry, it's easy:
   mailing list suffix.
 
 ## Table of Contents
-- [Joining the team](joining.md)
-- [Documentation structure](structure.md)
-- [Editing the PHP Manual](editing.md)
-- [Translating documentation](translating.md)
-- [Style guidelines](style.md)
+- [Joining the team](joining.php)
+- [Documentation structure](structure.php)
+- [Editing the PHP Manual](editing.php)
+- [Translating documentation](translating.php)
+- [Style guidelines](style.php)
 
 ## Appendices
-- [FAQ](faq.md)
-- [PHP Manual builds](builds.md)
+- [FAQ](faq.php)
+- [PHP Manual builds](builds.php)
 
 ## Feedback
 Feedback is most certainly welcome on this document. Without your submissions and input, this document wouldn't exist.

tutorial/joining.md

@@ -33,4 +33,4 @@ To request one, please fill in [this form](http://php.net/git-php.php).
 Provide links to your work that has already been committed and/or list your current patches.
 Basically, tell us what have done, to prove that you really need this account.
 
-The next chapter will explain how to get the manual sources and how are they [structured](structure.md).
+The next chapter will explain how to get the manual sources and how are they [structured](structure.php).

tutorial/structure.md

@@ -47,4 +47,4 @@ And OO extensions (such as imagick) contain:
 
 Note: *classname* is the lowercased name of the class, not a literal file or directory name.
 
-The next chapter will discuss how to [edit the manual sources](editing.md).
+The next chapter will discuss how to [edit the manual sources](editing.php).

tutorial/translating.md

@@ -1,7 +1,7 @@
 # Translating documentation
 
 **Watch out:** this chapter describes special parts of the whole editing process.
-You will also have to follow other steps from the [editing manual sources](editing.md) section.
+You will also have to follow other steps from the [editing manual sources](editing.php) section.
 
 Translating documentation into other languages might look like a complicated 
 process, but in fact, it's rather simple.