Merge pull request #334 from magento/jc_fix-broken-links

Fix broken links

Author: jcalcaben

_includes/php-dev/component-root.md

@@ -17,5 +17,5 @@ A component's root directory is the top-level directory for that component under
 ### Required files
 The following files are required for all components:
 
-*	`registration.php`: Among other things, this file specifies the directory in which the component is installed by vendors in production environments. By default, composer automatically installs components in the `<Magento root dir>/vendor` directory. For more information, see [Component registration]({{page.baseurl}}extension-dev-guide/component-registration.html).
-*	`composer.json`: Specifies component dependencies and other metadata. For more information, see [Composer integration]({{page.baseurl}}extension-dev-guide/composer-integration.html).
+*	`registration.php`: Among other things, this file specifies the directory in which the component is installed by vendors in production environments. By default, composer automatically installs components in the `<Magento root dir>/vendor` directory. For more information, see [Component registration]({{page.baseurl}}extension-dev-guide/build/component-registration.html).
+*	`composer.json`: Specifies component dependencies and other metadata. For more information, see [Composer integration]({{page.baseurl}}extension-dev-guide/build/composer-integration.html).

guides/v2.0/extension-dev-guide/depend-inj.md

@@ -79,7 +79,7 @@ The overall configuration is loaded in the following stages:
 2. Global (`<moduleDir>/etc/di.xml`)
 3. Area-specific (`<moduleDir>/etc/<area>/di.xml`)
 
-During [bootstrapping]({{site.mageurl}}config-guide/bootstrap/magento-bootstrap.html), each application entry point loads the appropriate `di.xml` files for the [area]({{site.mageurl}}architecture/modules/mod_and_areas.html) being requested.
+During [bootstrapping]({{page.baseurl}}config-guide/bootstrap/magento-bootstrap.html), each application entry point loads the appropriate `di.xml` files for the [area]({{page.baseurl}}architecture/modules/mod_and_areas.html) being requested.
 
 **Examples:**
 

guides/v2.0/howdoi/checkout/checkout_customize.md

@@ -110,7 +110,7 @@ To disable the component in your `checkout_index_index.xml` use the following in
 
 ## Remove a component
 
-To remove a component from layout rendering, you need to create a [plugin]({{page.baseurl}}guides/v2.1/extension-dev-guide/plugins.html) for the `\Magento\Checkout\Block\Checkout\LayoutProcessor::process` method. In your plugin, implement the around method removing the corresponding layout nodes at run-time. 
+To remove a component from layout rendering, you need to create a [plugin]({{page.baseurl}}extension-dev-guide/plugins.html) for the `\Magento\Checkout\Block\Checkout\LayoutProcessor::process` method. In your plugin, implement the around method removing the corresponding layout nodes at run-time. 
 
 The following sample is an example of the around method removing a component:
 
@@ -124,4 +124,4 @@ return $jsLayout;
 <div class="bs-callout bs-callout-info">
   <p>Disable vs remove a component </p>
 <p>If you disable a component, it is loaded but not rendered. If you remove a component, it is not loaded.</p>
-</div>
+</div>

guides/v2.0/howdoi/php/php_devs.md

@@ -12,7 +12,7 @@ github_link: howdoi/php/php_devs.md
 
 ## PHP development
 *	<a href="{{page.baseurl}}extension-dev-guide/build/composer-integration.html">Get to know Composer</a>
-*	<a href="{{page.baseurl}}extension-dev-guide/build.html">Build a module</a>
+*	<a href="{{page.baseurl}}extension-dev-guide/build/build.html">Build a module</a>
 *	<a href="{{page.baseurl}}extension-dev-guide/validate/validate.html">Validate a module</a>
 *	<a href="{{page.baseurl}}extension-dev-guide/package/package_module.html">Package a module</a>
 *	<a href="{{page.baseurl}}howdoi/php/php_clear-dirs.html">Clear directories during development</a>

guides/v2.0/howdoi/webapi/integration.md

@@ -15,12 +15,12 @@ An **integration** enables third-party services to call the Magento web APIs. Th
 
 Implementing a simple integration requires little knowledge of PHP or Magento internal processes. However, you will need a working knowledge of
 
-* [Magento REST or SOAP Web APIs](../../get-started/bk-get-started-api.html)
-* [Web API authentication](../../get-started/authentication/gs-authentication.html)
-* [OAuth-based authentication]( {{page.baseurl}}/get-started/authentication/gs-authentication-oauth.html )
+* [Magento REST or SOAP Web APIs]({{page.baseurl}}get-started/bk-get-started-api.html)
+* [Web API authentication]({{page.baseurl}}get-started/authentication/gs-authentication.html)
+* [OAuth-based authentication]( {{page.baseurl}}get-started/authentication/gs-authentication-oauth.html )
 
 
-Before you begin creating a module, make sure that you have a working installation of Magento 2.0, and the [Magento System Requirements](../../install-gde/system-requirements.html).
+Before you begin creating a module, make sure that you have a working installation of Magento 2.0, and the [Magento System Requirements]({{page.baseurl}}install-gde/system-requirements.html).
 
 To create an integration, follow these general steps:
 
@@ -43,7 +43,7 @@ To develop a module, you must:
     mkdir -p vendor/<vendor_name>/module-<module_name>/etc/integration
     mkdir -p vendor/<vendor_name>/module-<module_name>/Setup
    </pre>
-   For more detailed information, see [Create your component file structure](../../extension-dev-guide/module-file-structure.html).
+   For more detailed information, see [Create your component file structure]({{page.baseurl}}extension-dev-guide/build/module-file-structure.html).
 
 2. **Define your module configuration file.** The `etc/module.xml` file provides basic information about the module. Change directories to the `etc` directory and create the `module.xml` file. You must specify values for the following attributes:
 
@@ -108,7 +108,7 @@ To develop a module, you must:
     </pre>
 
 
-    For more information, see [Create a component]({{ site.gdejrl }}extension-dev-guide/build/create_component.html).
+    For more information, see [Create a component]({{page.baseurl}}extension-dev-guide/build/create_component.html).
 
 4. **Create a `registration.php` file** The `registration.php` registers the module with the Magento system. It must be placed in the module's root directory.
 
@@ -257,7 +257,7 @@ The  file defines which API resources the integration has access to.
 <tr>
 <td>endpoint_url</td>
 <td><p>Optional. The URL where OAuth credentials can be sent when using OAuth for token exchange. We strongly recommend using <code>https://</code>.</p>
-<p>See [OAuth-based authentication](../../get-started/authentication/gs-authentication-oauth.html) for details.</p></td>
+<p>See [OAuth-based authentication]({{page.baseurl}}get-started/authentication/gs-authentication-oauth.html) for details.</p></td>
 </tr>
 <tr>
 <td>identity_link_url</td>
@@ -314,8 +314,8 @@ The callback page must be able to perform the following tasks:
 * Save the access token and other OAuth parameters. The access token and OAuth parameters must be specified in the `Authorization` header in each call to Magento.
 
 ## Related Topics
-- [Web API authentication](../../get-started/authentication/gs-authentication.html)
+- [Web API authentication]({{page.baseurl}}get-started/authentication/gs-authentication.html)
 - [OAuth-based authentication]( {{page.baseurl}}/get-started/authentication/gs-authentication-oauth.html )
-- [Magento System Requirements](../../install-gde/system-requirements.html)
-- [Create the module file structure](../../extension-dev-guide/module-file-structure.html)
-- [Create a component](../../extension-dev-guide/create_component.html)
+- [Magento System Requirements]({{page.baseurl}}install-gde/system-requirements.html)
+- [Create the module file structure]({{page.baseurl}}extension-dev-guide/build/module-file-structure.html)
+- [Create a component]({{page.baseurl}}extension-dev-guide/build/create_component.html)