docs: gradle plugin guide link update

<div id="qv">

<h2>In this document</h2>

<ol>

  <li><a href="#workBuildVariants">Work with build variants</a></li>

  <li><a href="#buildConf">Build Configuration</a></li>

  <li><a href="#buildConv">Build by Convention</a></li>

  <li><a href="#projectModules">Project and Module Settings</a></li>

  <li><a href="#dependencies">Dependencies</a></li>

  <li><a href="#buildTasks">Build Tasks</a></li>

  <li><a href="#gradleWrapper">Gradle Wrapper</a></li>

  <li><a href="#buildVariants">Build Variants</a></li>

</ol>

<h2>Reference</h2>

<ul>

  <li>

  <a class="external-link" href="http://google.github.io/android-gradle-dsl">

    Android Plugin DSL</a>

  </li>

</ul>

<h2>See also</h2>

<ul>

Building and Running from Android Studio</a></li>

</ul>

<h2>Download</h2>

<div class="download-box">

  <a href="{@docRoot}shareables/sdk-tools/android-gradle-plugin-dsl.zip"

    class="button">Plugin Language Reference</a>

  <p class="filename">android-gradle-plugin-dsl.zip</p>

</div>

</div>

</div>

<p>The output of the build is the same whether you are building a project from the command line,

on a remote machine, or using Android Studio.</p>

<h2 id="buildConf">Build configuration</h2>

<h2 id="buildConf">Build Configuration</h2>

<p>The build configuration for your project is defined inside <code>build.gradle</code> files,

which are plain text files that use the syntax and options from Gradle and the Android plugin

language that you can use to define custom build logic and to interact with the Android-specific

elements provided by the Android plugin for Gradle.</p>

<h2 id="buildConv">Build by convention</h2>

<h2 id="buildConv">Build by Convention</h2>

<p>The Android Studio build system assumes <em>sensible defaults</em> for the project structure

and other build options. If your project adheres to these conventions, your Gradle build files are

you need to replace the default source folders in your module directories, you can configure a new

directory structure in the module's build file. </p>

<h2 id="projectModules">Projects and modules build settings</h2>

<h2 id="projectModules">Project and Module Settings</h2>

<p>A <em>project</em> in Android Studio represents the top-level Android development structure.

Android Studio projects contain project files and one or more application modules. A

    </dd>

</dl>

<h2 id="buildTasks">Build tasks</h2>

<h2 id="buildTasks">Build Tasks</h2>

<p>The Android Studio build system defines a hierarchical set of build tasks: the top-level or

anchor tasks invoke dependent tasks to produce their collective build outcomes. The top-level build

and <a href="{@docRoot}tools/building/building-cmdline.html">Build the project from

the command line</a>.</p>

<h2 id="gradleWrapper">The Gradle wrapper</h2>

<h2 id="gradleWrapper">Gradle Wrapper</h2>

<p>Android Studio projects contain the <em>Gradle wrapper</em>, which consists of:</p>

scripts and JAR from a trusted source, such as those generated by Android Studio. </p>

<h2 id="buildVariants"> Build variants</h2>

<h2 id="buildVariants">Build Variants</h2>

<p>Each version of your app is represented in the build system by a <em>build variant</em>.

Build variants are combinations of product flavors and build types. Product flavors represent