diff --git a/src/main/markdown/articles/articles.md b/src/main/markdown/articles/articles.md
index bbe019f2d..c63732ed6 100644
--- a/src/main/markdown/articles/articles.md
+++ b/src/main/markdown/articles/articles.md
@@ -59,10 +59,10 @@ JSON services across the web.
 
 **GWT Tutorial** is a step-by-step guide to a complete GWT project. It walks through a project to explain the essentials as well as some of the advanced concepts of GWT 2. Level - Beginner and Intermediate. 
 
-*   [Exporting Libraries Developed in GWT to JavaScript](//code.google
+*   [Exporting Libraries Developed in GWT to JavaScript](https://code.google
 .com/p/gwtchismes/wiki/Tutorial_ExportingGwtLibrariesToJavascript_en) - _Contributed by Manuel Carrasco Moñino_
 
-This article describes how you can export GWT defined methods to the outside JavaScript world, allowing your GWT application to provide an API for external consumption. It covers both a manual technique which uses only the GWT core library, as well as an even easier technique which uses of the [GWT-Exporter library](//code.google.com/p/gwt-exporter).
+This article describes how you can export GWT defined methods to the outside JavaScript world, allowing your GWT application to provide an API for external consumption. It covers both a manual technique which uses only the GWT core library, as well as an even easier technique which uses of the [GWT-Exporter library](https://code.google.com/p/gwt-exporter).
 
 If you believe that any resource should be added or removed from the list above, please [let us
 know](mailto:Google-Web-Toolkit+owner@googlegroups.com).
diff --git a/src/main/markdown/articles/gwt-iphone.md b/src/main/markdown/articles/gwt-iphone.md
index a7470b26e..e5c4d2dd8 100644
--- a/src/main/markdown/articles/gwt-iphone.md
+++ b/src/main/markdown/articles/gwt-iphone.md
@@ -14,7 +14,7 @@ code, we decided to write an application that we would find useful and that
 shows off the cool features of the iPhone. The result is the
 GWT Feed Reader, an RSS feed reader that uses the
 [Google
-AJAX Feed API](//developers.google.com/feed/) with a user interface optimized for the iPhone. This article
+AJAX Feed API](https://developers.google.com/feed/) with a user interface optimized for the iPhone. This article
 will discuss what we've learned from writing this RSS reader.
 
 The good news is that writing a GWT application that
@@ -180,7 +180,7 @@ two HTTP round-trips.
 The Feed Reader needs to get its feed data from somewhere. Enough
 of the
 [Google
-AJAX Feed API](//developers.google.com/feed/) was imported with Java bindings using the
+AJAX Feed API](https://developers.google.com/feed/) was imported with Java bindings using the
 [GWT
 JavaScript Interop](http://code.google.com/p/gwt-api-interop) project. This eliminated the need to hand-write
 JSNI calls to the underlying JavaScript API by declaring the binding with a
diff --git a/src/main/markdown/articles/using_gwt_for_json_mashups.md b/src/main/markdown/articles/using_gwt_for_json_mashups.md
index 39a611025..04bf2a7aa 100644
--- a/src/main/markdown/articles/using_gwt_for_json_mashups.md
+++ b/src/main/markdown/articles/using_gwt_for_json_mashups.md
@@ -44,7 +44,7 @@ The latter two techniques, however, fetch the strings using dynamic `<script>` t
 
 ## High-level design
 
-Now that we have the JSON basics in hand, what about my project? The task I was working on involved mashing up data from another service--specifically, Google Base. This means that I needed to use the [Google Data API](http://code.google.com/apis/gdata/index.html) for fetching information. Google's GData servers provide XML, JSON, and JSONP-style interfaces, to allow developers maximum flexibility in building applications. For my project, I wanted to build an in-browser mashup, which means I needed to use the [Google Data API's  JSONP-style interface](//developers.google.com/gdata/docs/json).
+Now that we have the JSON basics in hand, what about my project? The task I was working on involved mashing up data from another service--specifically, Google Base. This means that I needed to use the [Google Data API](http://code.google.com/apis/gdata/index.html) for fetching information. Google's GData servers provide XML, JSON, and JSONP-style interfaces, to allow developers maximum flexibility in building applications. For my project, I wanted to build an in-browser mashup, which means I needed to use the [Google Data API's  JSONP-style interface](https://developers.google.com/gdata/docs/json).
 
 Since GWT applications are written in Java, there is a compilation phase that compiles the Java source to JavaScript. The compiler also optimizes the generated code, and one of the optimizations it performs is code obfuscation, which makes the output smaller and thus faster to load. A downside of this, though, is that the function names in the output JavaScript code are unpredictable. This makes it difficult to specify a callback function name to a JSONP service.
 
diff --git a/src/main/markdown/doc/latest/DevGuideCompileReport.md b/src/main/markdown/doc/latest/DevGuideCompileReport.md
index 2949df175..857a12d35 100644
--- a/src/main/markdown/doc/latest/DevGuideCompileReport.md
+++ b/src/main/markdown/doc/latest/DevGuideCompileReport.md
@@ -61,7 +61,7 @@ _Figure 3: Package breakdown_
 
 This overview breakdown can be particularly useful, for example, to learn how much of the code size is caused by JRE code. For example, if you see that your use of java.util.HashSet causes your application to grow too big, you may find a way to do without java.util.HashSet in your code.
 
-### Dependencie
+### Dependencies
 
 At some point you will try to get something moved out of the initial download fragment, but the GWT compiler will put it there anyway. Sometimes you can quickly figure out why, but other times it will not be obvious at all. The way to find out is to look through the dependencies that are reported in the Compile Report.
 The most common example is that you expected something (say, a class) to be left out of the initial download, but it was not. To find out why, browse to that class via the "initial download" code subset (from the Overview, click on the relevant permutation, then click on the "Report" link below "Initial download size".  Then click on the class's package). Once you click on the class, you can look at a chain of dependencies leading back to the application's main entry point. This is the chain of dependencies that causes GWT to think the item must be in the initial download. Try to rearrange the code to break one of the links in that chain.
diff --git a/src/main/markdown/doc/latest/DevGuideDeploying.md b/src/main/markdown/doc/latest/DevGuideDeploying.md
index 2b9a37ac8..7e84f3310 100644
--- a/src/main/markdown/doc/latest/DevGuideDeploying.md
+++ b/src/main/markdown/doc/latest/DevGuideDeploying.md
@@ -80,4 +80,4 @@ and then deploy your application from the war output directory by invoking the a
 <appengine_home_dir>/appcfg.sh update war
 ```
 
-You will need to have your appengine-web.xml properly configured beforehand, as well as ensure that you have created a Google App Engine account and an application space for your GWT application. You can read the [App Engine docs](//developers.google.com/appengine/docs/java/gettingstarted/) for more information.
+You will need to have your appengine-web.xml properly configured beforehand, as well as ensure that you have created a Google App Engine account and an application space for your GWT application. You can read the [App Engine docs](https://developers.google.com/appengine/docs/java/gettingstarted/) for more information.
diff --git a/src/main/markdown/doc/latest/FAQ_DebuggingAndCompiling.md b/src/main/markdown/doc/latest/FAQ_DebuggingAndCompiling.md
index 728398da3..08e4b7623 100644
--- a/src/main/markdown/doc/latest/FAQ_DebuggingAndCompiling.md
+++ b/src/main/markdown/doc/latest/FAQ_DebuggingAndCompiling.md
@@ -231,7 +231,7 @@ At this point, you should be ready to go. That is, of course, if you're planning
 
 ## Does the new WAR output directory layout require me to use Java on the server-side?<a id="Does_the_new_war_output_directory_layout_require_java_on_the_server"></a>
 
-Like in previous versions of GWT, you can always use the server-side of your choice to deploy your GWT application. The new WAR output directory structure that the GWT compiler uses to generate output was introduced in GWT 1.6 to make it easier for developers who use Java on the server-side to deploy their applications directly from the generated output, as is the case for the [Google Plugin for Eclipse.](//developers.google.com/eclipse/)
+Like in previous versions of GWT, you can always use the server-side of your choice to deploy your GWT application. The new WAR output directory structure that the GWT compiler uses to generate output was introduced in GWT 1.6 to make it easier for developers who use Java on the server-side to deploy their applications directly from the generated output, as is the case for the [Google Plugin for Eclipse.](https://developers.google.com/eclipse/)
 
 All you need to do to deploy your GWT application your custom web server is to extract the
 important files generated during the GWT compilation and place them on your web server.
diff --git a/src/main/markdown/doc/latest/FAQ_Troubleshooting.md b/src/main/markdown/doc/latest/FAQ_Troubleshooting.md
index e44d8aa9c..e617fb873 100644
--- a/src/main/markdown/doc/latest/FAQ_Troubleshooting.md
+++ b/src/main/markdown/doc/latest/FAQ_Troubleshooting.md
@@ -304,7 +304,7 @@ Finding entry point classes
 Failure to load module 'com.google.gwt.sample.stockwatcher.StockWatcher'
 ```
 
-This problem is most often seen when creating a launch configuration manually.  The [Google Plugin for Eclipse](//developers.google.com/eclipse) handles adding source roots to the classpath automatically.
+This problem is most often seen when creating a launch configuration manually.  The [Google Plugin for Eclipse](https://developers.google.com/eclipse) handles adding source roots to the classpath automatically.
 
 One of the most common problems when creating launch configurations manually in GWT is to omit the application source code path from the Java classpath. The [GWT compiler](DevGuideCompilingAndDebugging.html#DevGuideJavaToJavaScriptCompiler) and [development mode](DevGuideCompilingAndDebugging.html#DevGuideDevMode) shell rely on the module
 source code to build your application, and both use the Java classpath to find the .java source files.
@@ -348,7 +348,7 @@ java.security.AccessControlException: access denied
 
 ```
 
-The problem occurs if you mistakenly enabled the [Google App Engine](https://developers.google.com/appengine) feature for your project when you created the project, or at a later time during development, and have server-side libraries or classes packaged with your GWT application war folder that violate the [Java App Engine sandbox](//developers.google.com/appengine/docs/whatisgoogleappengine).
+The problem occurs if you mistakenly enabled the [Google App Engine](https://developers.google.com/appengine) feature for your project when you created the project, or at a later time during development, and have server-side libraries or classes packaged with your GWT application war folder that violate the [Java App Engine sandbox](https://developers.google.com/appengine/docs/whatisgoogleappengine).
 
 #### Workaround
 
@@ -358,7 +358,7 @@ If you don't intend on using Google App Engine for your project, simply remove t
 2.  In the App Engine property menu, deselect the **Use Google App Engine** checkbox.
 3.  Click **OK**.
 
-If you intend to use Google App Engine, you will need to remove any use of server-side libraries that are violating the security constraints of the App Engine sandbox from your project. For more information on the support available in the App Engine sandbox, check out the [App Engine documentation.](//developers.google.com/appengine/docs)
+If you intend to use Google App Engine, you will need to remove any use of server-side libraries that are violating the security constraints of the App Engine sandbox from your project. For more information on the support available in the App Engine sandbox, check out the [App Engine documentation.](https://developers.google.com/appengine/docs)
 
 ## Image Bundles<a id="Image_Bundles"></a>
 
diff --git a/src/main/markdown/doc/latest/tutorial/appengine.md b/src/main/markdown/doc/latest/tutorial/appengine.md
index a5be4d227..3d54ca5f7 100644
--- a/src/main/markdown/doc/latest/tutorial/appengine.md
+++ b/src/main/markdown/doc/latest/tutorial/appengine.md
@@ -3,7 +3,7 @@ Deploy to GAE
 
 At this point, you've created the initial implementation of the StockWatcher application, simulating stock data in the client-side code.
 
-In this section, you'll deploy this application on [Google App Engine](//developers.google.com/appengine).  Also, you'll learn about some of the App Engine service APIs and use them to personalize the StockWatcher application so that users can log into their Google Account and retrieve their list of stocks.
+In this section, you'll deploy this application on [Google App Engine](https://developers.google.com/appengine).  Also, you'll learn about some of the App Engine service APIs and use them to personalize the StockWatcher application so that users can log into their Google Account and retrieve their list of stocks.
 
 1.  [Get started with App Engine](#intro)
 2.  [Deploy the application to App Engine](#deploy)
@@ -22,7 +22,7 @@ This tutorial builds on the GWT concepts and the StockWatcher application create
 
 ### Download the App Engine SDK
 
-If you plan to use Eclipse, you can download the App Engine SDK with the [Google Plugin for Eclipse](//developers.google.com/appengine/docs/java/tools/eclipse). Or [download](//developers.google.com/appengine/downloads) the App Engine SDK for Java separately.
+If you plan to use Eclipse, you can download the App Engine SDK with the [Google Plugin for Eclipse](https://developers.google.com/appengine/docs/java/tools/eclipse). Or [download](https://developers.google.com/appengine/downloads) the App Engine SDK for Java separately.
 
 
 ### Set up a project
@@ -31,7 +31,7 @@ If you plan to use Eclipse, you can download the App Engine SDK with the [Google
 
 If you initially created your StockWatcher Eclipse project using the Google Plugin for Eclipse with both GWT and Google App Engine enabled, your project is already ready to run on App Engine.  If not:
 
-1.  If you haven't yet, install the [Google Plugin for Eclipse](//developers.google.com/appengine/docs/java/tools/eclipse) with both GWT and App Engine SDK and restart Eclipse.
+1.  If you haven't yet, install the [Google Plugin for Eclipse](https://developers.google.com/appengine/docs/java/tools/eclipse) with both GWT and App Engine SDK and restart Eclipse.
 2.  Complete the [Build a Sample GWT Application](gettingstarted.html) tutorial, making sure to create a project with both GWT and Google App Engine enabled.  Alternatively, if you would like to skip the Build a Sample GWT Application tutorial, then [download](http://code.google.com/p/google-web-toolkit/downloads/detail?name=Tutorial-GettingStartedAppEngine-2.1.zip), unzip and import the StockWatcher Eclipse project.  To import the project:
 
     1.  In the File menu, select the Import... menu option.
@@ -41,7 +41,7 @@ If you initially created your StockWatcher Eclipse project using the Google Plug
 
 #### Set up a project (without Eclipse)
 
-1.  If you haven't yet, download the [App Engine SDK](//developers.google.com/appengine/downloads) for Java.
+1.  If you haven't yet, download the [App Engine SDK](https://developers.google.com/appengine/downloads) for Java.
 2.  Complete the [Build a Sample GWT Application](gettingstarted.html) tutorial,  using webAppCreator to create a GWT application.  Alternatively, If you would like to skip the Build a Sample GWT Application tutorial, then download and unzip [this file](http://code.google.com/p/google-web-toolkit/downloads/detail?name=Tutorial-GettingStarted-2.1.zip).  Edit the gwt.sdk property in the StockWatcher/build.xml, then proceed with the modifications below.
 3.  App Engine requires its own web application deployment descriptor.  Create a file StockWatcher/war/WEB-INF/appengine-web.xml with these contents:
 
@@ -52,9 +52,9 @@ If you initially created your StockWatcher Eclipse project using the Google Plug
         </appengine-web-app>
 
     Substitute your App Engine application ID on the second line. Read more about
-[appengine-web.xml](//developers.google.com/appengine/docs/java/config/appconfig).
+[appengine-web.xml](https://developers.google.com/appengine/docs/java/config/appconfig).
 
-4.  As we will be using [Java Data Objects (JDO)](//developers.google.com/appengine/docs/java/gettingstarted/usingdatastore) later for storing data, create a file StockWatcher/src/META-INF/jdoconfig.xml with these contents:
+4.  As we will be using [Java Data Objects (JDO)](https://developers.google.com/appengine/docs/java/gettingstarted/usingdatastore) later for storing data, create a file StockWatcher/src/META-INF/jdoconfig.xml with these contents:
 
         <?xml version="1.0" encoding="utf-8"?>
         <jdoconfig xmlns="http://java.sun.com/xml/ns/jdo/jdoconfig"
@@ -71,7 +71,7 @@ If you initially created your StockWatcher Eclipse project using the Google Plug
         </jdoconfig>
 
     You will reference this configuration later by its name "transactions-optional". Read more about
-[jdoconfig.xml](//developers.google.com/appengine/docs/java/datastore/usingjdo).
+[jdoconfig.xml](https://developers.google.com/appengine/docs/java/datastore/usingjdo).
 
 5.  The GWT ant build file needs to be modified to support DataNucleus JDO compilation and use of the App Engine development server.  Edit StockWatcher/build.xml and add the following:
 
@@ -509,7 +509,7 @@ If you run the application in development mode with the App Engine development s
 
 ### Overview
 
-The datastore service available to the App Engine Java runtime is the same service available to the Python runtime.  To access this service in Java, you may use the low-level [datastore API](//developers.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/package-summary), [Java Data Objects (JDO)](//developers.google.com/appengine/docs/java/datastore/usingjdo), or [Java Persistence API (JPA)](//developers.google.com/appengine/docs/java/datastore/usingjpa).  For this sample we will use JDO.
+The datastore service available to the App Engine Java runtime is the same service available to the Python runtime.  To access this service in Java, you may use the low-level [datastore API](https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/package-summary), [Java Data Objects (JDO)](https://developers.google.com/appengine/docs/java/datastore/usingjdo), or [Java Persistence API (JPA)](https://developers.google.com/appengine/docs/java/datastore/usingjpa).  For this sample we will use JDO.
 
 ### Define the Stock RPC service
 
@@ -1085,6 +1085,6 @@ Users can now sign in to Google Account and manage their own stock lists in the
 
 ### Learn more about App Engine
 
-The App Engine [Java Getting Started tutorial](//developers.google.com/appengine/docs/java/gettingstarted) gives more details on building an App Engine application including topics such as creating a project from scratch, using JSPs, managing different application versions, and more details on the web application descriptor files.
+The App Engine [Java Getting Started tutorial](https://developers.google.com/appengine/docs/java/gettingstarted) gives more details on building an App Engine application including topics such as creating a project from scratch, using JSPs, managing different application versions, and more details on the web application descriptor files.
 
-The App Engine [Java documentation](//developers.google.com/appengine/docs/java) covers the User service and datastore service in greater detail.  In particular, it documents how to use JPA to access the datastore service.  Other services documented include Memcache, HTTP client, and, Java Mail.  The limitations of the App Engine Java runtime are also itemized.
+The App Engine [Java documentation](https://developers.google.com/appengine/docs/java) covers the User service and datastore service in greater detail.  In particular, it documents how to use JPA to access the datastore service.  Other services documented include Memcache, HTTP client, and, Java Mail.  The limitations of the App Engine Java runtime are also itemized.
diff --git a/src/main/markdown/doc/latest/tutorial/clientserver.md b/src/main/markdown/doc/latest/tutorial/clientserver.md
index 8a761b1a5..29b389a74 100644
--- a/src/main/markdown/doc/latest/tutorial/clientserver.md
+++ b/src/main/markdown/doc/latest/tutorial/clientserver.md
@@ -34,7 +34,7 @@ If you're creating a mashup application that needs to use data from one or more
 
 To try this out, see the tutorial, [Making Cross-Site Requests](Xsite.html).
 
-Note: There is a variety of public sources of JSON-formatted data you can practice with, including [Google Data APIs](//developers.google.com/gdata/) and [Yahoo! Web Services](http://developer.yahoo.com/).
+Note: There is a variety of public sources of JSON-formatted data you can practice with, including [Google Data APIs](https://developers.google.com/gdata/) and [Yahoo! Web Services](http://developer.yahoo.com/).
 
 ## Making Asynchronous Calls
 
diff --git a/src/main/markdown/doc/latest/tutorial/index.md b/src/main/markdown/doc/latest/tutorial/index.md
index 59eeec29b..a6de4ff25 100644
--- a/src/main/markdown/doc/latest/tutorial/index.md
+++ b/src/main/markdown/doc/latest/tutorial/index.md
@@ -15,7 +15,7 @@ Before you begin these tutorials, we assume that you've done the following:
     *  In these tutorials, we use [Eclipse](http://www.eclipse.org/) because it is open source. However, GWT does not tie you to Eclipse. You can use [IntelliJ](http://www.jetbrains.com/idea/), [NetBeans](http://www.netbeans.org/) or any Java IDE you prefer. If you use a Java IDE other than Eclipse, the screenshots and some of the specific instructions in the tutorial will be different, but the basic GWT concepts will be the same.
     *  If your Java IDE does not include Apache Ant support, you can download and unzip [Ant](http://ant.apache.org) to easily compile and run GWT applications.
 *   Installed the Google Plugin for Eclipse.
-    *  The [Google Plugin for Eclipse](//developers.google.com/appengine/docs/java/tools/eclipse) adds functionality to Eclipse for creating and developing GWT applications.
+    *  The [Google Plugin for Eclipse](https://developers.google.com/appengine/docs/java/tools/eclipse) adds functionality to Eclipse for creating and developing GWT applications.
 *   Downloaded Google Web Toolkit.
     *  Google Web Toolkit can be downloaded with the Google Plugin for Eclipse.  Alternatively, download the most recent distribution of [Google Web Toolkit](../../../download.html) for your operating system.
 *   Unzipped the GWT distribution in directory you want to run it in.
@@ -24,7 +24,7 @@ Before you begin these tutorials, we assume that you've done the following:
 You may also optionally do the following:
 
 *   Install the Google App Engine SDK.
-    *  Google App Engine allows you to run Java web applications, including GWT applications, on Google's infrastructure.  The App Engine SDK can be downloaded with the Google Plugin for Eclipse.  Alternatively, download the [App Engine SDK](//developers.google.com/appengine/downloads) for Java separately.
+    *  Google App Engine allows you to run Java web applications, including GWT applications, on Google's infrastructure.  The App Engine SDK can be downloaded with the Google Plugin for Eclipse.  Alternatively, download the [App Engine SDK](https://developers.google.com/appengine/downloads) for Java separately.
 *   [Create and run your first web application](../../../gettingstarted.html#create) - A few, simple steps to familiarize you with the command line commands.
 
 ## GWT Tutorials <a id="gwt_tutorials"></a>
@@ -56,4 +56,4 @@ You may also optionally do the following:
 ### Deploying to Google App Engine
 
 *   [Deploying to Google App Engine](appengine.html)
-    *  Deploy a GWT application to [App Engine](//developers.google.com/appengine).
+    *  Deploy a GWT application to [App Engine](https://developers.google.com/appengine).
diff --git a/src/main/markdown/examples.md b/src/main/markdown/examples.md
index a9a3a7949..8a2ca9c6e 100644
--- a/src/main/markdown/examples.md
+++ b/src/main/markdown/examples.md
@@ -72,7 +72,7 @@ Examples
 
 If you're like us, the first thing you want to do is see examples of what you can do with GWT.
 
-*   [Samples](#samples) are included in the SDK for you to play around with and build off of. A few are below. Some are from the [App Engine SDK](//developers.google.com/appengine/) that use GWT for their front end.
+*   [Samples](#samples) are included in the SDK for you to play around with and build off of. A few are below. Some are from the [App Engine SDK](https://developers.google.com/appengine/) that use GWT for their front end.
 *   [Real world projects](#real-world-projects) let you see the real power of GWT, with complex applications that developers are building.
 
 If you'd like to see who else is using GWT, check out the [GWT Gallery](http://gwtgallery.appspot.com). You'll be able to find other applications and libraries built with GWT, comment on them, rate them, and search for them by tag or by name. You can also [submit your own entry](http://gwtgallery.appspot.com/submit) if you have a project that  you want to share.
diff --git a/src/main/markdown/index.md b/src/main/markdown/index.md
index d77624b6f..e4cdd3de6 100644
--- a/src/main/markdown/index.md
+++ b/src/main/markdown/index.md
@@ -24,7 +24,7 @@ GWT (pronounced 'gwit') is the official open source project for GWT releases 2.7
         <div style="margin-left: 112px; margin-bottom: 10px;">
           <div style="font-size: 120%; font-weight: bold;"><a href="overview.html">Learn More</a></div>
           <div style="padding-top: 5px; line-height: 125%;">
-            Learn about GWT, the features and tools it offers, and how you can quickly develop performance AJAX applications across all major browsers.<br /><br />
+            Learn about GWT, the features and tools it offers, and how you can quickly develop high-performance AJAX applications across all major browsers.<br /><br />
           </div>
         </div>
       </td>