Merge "com.google.gwt.i18n.rebind.keygen.MD5KeyGenerator is deprecated in favor of com.google.gwt.i18n.server.keygen.MD5KeyGenerator"
diff --git a/src/main/markdown/articles/gwt-iphone.md b/src/main/markdown/articles/gwt-iphone.md
index 8b88b3c..b62cc72 100644
--- a/src/main/markdown/articles/gwt-iphone.md
+++ b/src/main/markdown/articles/gwt-iphone.md
@@ -2,14 +2,15 @@
 <br>
 <i>July 2007</i>
 
+<p><i>This article is obsolete, but may be of historical interest.</i></p>
+
 <p>
 It's now been a few weeks since the release of GWT 1.4 and Apple's iPhone.&nbsp;
 We've spent some of that time learning how to optimize GWT
 applications for the iPhone.&nbsp; Since nothing beats experience with real
 code, we decided to write an application that we would find useful and that
 shows off the cool features of the iPhone.&nbsp; The result is the
-<a href="http://gwt.google.com/samples/GwtFeedReader">GWT
-Feed Reader</a>, an RSS feed reader that uses the
+GWT Feed Reader, an RSS feed reader that uses the
 <a href="//developers.google.com/feed/">Google
 AJAX Feed API</a> with a user interface optimized for the iPhone. This article
 will discuss what we've learned from writing this RSS reader.
diff --git a/src/main/markdown/articles/security_for_gwt_applications.md b/src/main/markdown/articles/security_for_gwt_applications.md
index f1ac39e..6dedf4d 100644
--- a/src/main/markdown/articles/security_for_gwt_applications.md
+++ b/src/main/markdown/articles/security_for_gwt_applications.md
@@ -275,7 +275,7 @@
 
 <h4>Protecting Your Application</h4>
 
-<p>If you are using the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html">RequestBuilder</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/RequestCallback.html">RequestCallback</a> classes in GWT, you can implement XSRF protection by setting a custom header to contain the value of your cookie. Here is some sample code:</p>
+<p>If you are using the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html">RequestBuilder</a> and <a href="/javadoc/latest/com/google/gwt/http/client/RequestCallback.html">RequestCallback</a> classes in GWT, you can implement XSRF protection by setting a custom header to contain the value of your cookie. Here is some sample code:</p>
 
 <pre>
 RequestBuilder rb = new RequestBuilder(RequestBuilder.POST, url);
diff --git a/src/main/markdown/doc/latest/DevGuide.md b/src/main/markdown/doc/latest/DevGuide.md
index 1608ae6..743908e 100644
--- a/src/main/markdown/doc/latest/DevGuide.md
+++ b/src/main/markdown/doc/latest/DevGuide.md
@@ -34,7 +34,7 @@
 
 <h2>Developer Guide</h2>
 <ol class="toc">
- <li><a href="ReleaseNotes.html">What's New in GWT 2.5.1?</a></li>
+ <li><a href="ReleaseNotes.html">What's New in GWT 2.6.1?</a></li>
   <li><a href="DevGuideOrganizingProjects.html">Organize Projects</a> &ndash; Describes conventions to identify which code is intended to run on the client browser, the server, or both</li>
   <li><a href="DevGuideCompilingAndDebugging.html">Compile &amp; Debug</a> &ndash; Describes development and production modes</li>
   <li><a href="DevGuideCodingBasics.html">Coding Basics</a> &ndash; Describes GWT programming fundamentals
diff --git a/src/main/markdown/doc/latest/DevGuideA11y.md b/src/main/markdown/doc/latest/DevGuideA11y.md
index 6478c04..bbe4b70 100644
--- a/src/main/markdown/doc/latest/DevGuideA11y.md
+++ b/src/main/markdown/doc/latest/DevGuideA11y.md
@@ -63,15 +63,15 @@
 <p>The ARIA standard specifies the HTML attribute type for the state and property
 values. These attribute types are supported in the new library with compile-time checks. Enumerations have been added for
 HTML attributes of type token like 'aria-dropeffect' property type, 'aria-checked' type etc. There is a common type added for
-IDREF(S) in the class. All the states and properties are defined in the <a href="/javadoc/latest/com/google/gwt/aria/client/State.html">State</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/aria/client/Property.html">Property</a> classes. The
+IDREF(S) in the class. All the states and properties are defined in the <a href="/javadoc/latest/com/google/gwt/aria/client/State.html">State</a> and <a href="/javadoc/latest/com/google/gwt/aria/client/Property.html">Property</a> classes. The
 <tt>tabIndex</tt> attribute has also been added as an extra attribute in the ARIA standard and we have <a href="/javadoc/latest/com/google/gwt/aria/client/ExtraAttribute.html">added it to the library</a>. We encourage users to get access to states and
 properties through the role by getting it from the <a href="/javadoc/latest/com/google/gwt/aria/client/Roles.html">Roles factory</a> because
 the factory checks that the state or property is supported for the role.</p>
 
 <p>Many GWT widgets now have keyboard accessibility and ARIA properties. These include <a href="/javadoc/latest/com/google/gwt/user/client/ui/CustomButton.html">CustomButton</a>,
- <a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/TreeItem.html">TreeItem</a>,
- <a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/MenuItem.html">MenuItem</a>,
- <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabBar.html">TabBar</a>, and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/TabPanel.html">TabPanel</a>.
+ <a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a>, <a href="/javadoc/latest/com/google/gwt/user/client/ui/TreeItem.html">TreeItem</a>,
+ <a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a>, <a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuItem.html">MenuItem</a>,
+ <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabBar.html">TabBar</a>, and <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabPanel.html">TabPanel</a>.
  Also, all widgets that inherit from FocusWidget now have a tabindex by default, allowing for better keyboard navigation.</p>
 
 
@@ -216,7 +216,7 @@
 
 <h2 id="selectionChanges">Indicating Selection Changes</h2>
 
-<p>Some widgets, such as GWT's <a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a> widgets,
+<p>Some widgets, such as GWT's <a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a> widgets,
 consist of a container with a set of items. The container has a naturally focusable DOM element, but the items
 themselves do not. The focusable element receives all keyboard input, and causes visual changes in the contained items
 to indicate a change in item selection. For example, GWT's Tree widget contains <a href="/javadoc/latest/com/google/gwt/user/client/ui/TreeItem.html">TreeItems</a>; both of these elements are made up of <tt>div</tt> elements. However, the Tree also
diff --git a/src/main/markdown/doc/latest/DevGuideClientBundle.md b/src/main/markdown/doc/latest/DevGuideClientBundle.md
index 0a8cd48..233b339 100644
--- a/src/main/markdown/doc/latest/DevGuideClientBundle.md
+++ b/src/main/markdown/doc/latest/DevGuideClientBundle.md
@@ -102,7 +102,7 @@
 
 
 
-<p>Each subtype of <tt><a href="/javadoc/latest/index.html?com/google/gwt/resources/client/ResourcePrototype.html">ResourcePrototype</a></tt> must define a <tt><a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/index.html?com/google/gwt/resources/ext/ResourceGeneratorType.html">@ResourceGeneratorType</a></tt> annotation whose value is a concrete Java class that extends <tt><a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/index.html?com/google/gwt/resources/ext/ResourceGenerator.html">ResourceGenerator</a></tt>.  The instance of the <tt>ResourceGenerator</tt> is responsible for accumulation (or bundling) of incoming resource data as well as a small degree of code generation to assemble the concrete implementation of the <tt>ClientBundle</tt> class.  Implementors of <tt>ResourceGenerator</tt> subclasses can expect that only one <tt>ResourceGenerator</tt> will be created for a given type of resource within a <tt>ClientBundle</tt> interface. </p>
+<p>Each subtype of <tt><a href="/javadoc/latest/index.html?com/google/gwt/resources/client/ResourcePrototype.html">ResourcePrototype</a></tt> must define a <tt><a href="/javadoc/latest/index.html?com/google/gwt/resources/ext/ResourceGeneratorType.html">@ResourceGeneratorType</a></tt> annotation whose value is a concrete Java class that extends <tt><a href="/javadoc/latest/index.html?com/google/gwt/resources/ext/ResourceGenerator.html">ResourceGenerator</a></tt>.  The instance of the <tt>ResourceGenerator</tt> is responsible for accumulation (or bundling) of incoming resource data as well as a small degree of code generation to assemble the concrete implementation of the <tt>ClientBundle</tt> class.  Implementors of <tt>ResourceGenerator</tt> subclasses can expect that only one <tt>ResourceGenerator</tt> will be created for a given type of resource within a <tt>ClientBundle</tt> interface. </p>
 
 <p>The methods on a <tt>ResourceGenerator</tt> are called in the following order
 
@@ -158,7 +158,7 @@
 
 <h2 id="TextResource">TextResource and ExternalTextResource</h2>
 
-<p>The related resource types <a href="/javadoc/latest/index.html?com/google/gwt/resources/client/TextResource.html">TextResource</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/index.html?com/google/gwt/resources/client/ExternalTextResource.html">ExternalTextResource</a> provide access to static text content.  The main difference between these two types is that the former interns the text into the compiled JavaScript, while the latter bundles related text resources into a single file, which is accessed asynchronously.</p>
+<p>The related resource types <a href="/javadoc/latest/index.html?com/google/gwt/resources/client/TextResource.html">TextResource</a> and <a href="/javadoc/latest/index.html?com/google/gwt/resources/client/ExternalTextResource.html">ExternalTextResource</a> provide access to static text content.  The main difference between these two types is that the former interns the text into the compiled JavaScript, while the latter bundles related text resources into a single file, which is accessed asynchronously.</p>
 
 <pre class="prettyprint">interface Resources extends ClientBundle {
   Resources INSTANCE = GWT.create(Resources.class);
@@ -657,7 +657,7 @@
 ImageResource logo();</pre>
 
 
-  <li><a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/test/com/google/gwt/resources/rg">Current auto-RTL test cases</a> </li></ul>
+  <li><a href="https://gwt.googlesource.com/gwt/+/master/user/test/com/google/gwt/resources/rg">Current auto-RTL test cases</a> </li></ul>
 
 <h4 id="Selector_obfuscation">Selector obfuscation</h4>
 
diff --git a/src/main/markdown/doc/latest/DevGuideCodingBasicsDeferred.md b/src/main/markdown/doc/latest/DevGuideCodingBasicsDeferred.md
index 32758e2..9150f72 100644
--- a/src/main/markdown/doc/latest/DevGuideCodingBasicsDeferred.md
+++ b/src/main/markdown/doc/latest/DevGuideCodingBasicsDeferred.md
@@ -62,12 +62,12 @@
 <p>For example, the following configuration invokes deferred binding for the <a href="/javadoc/latest/com/google/gwt/user/client/ui/PopupPanel.html">PopupPanel</a> widget:</p>
 
 <ul>
-<li>Top level <i>&lt;module&gt;</i>.gwt.xml <i><strong>inherits</strong></i> <a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/User.gwt.xml">com.google.gwt.user.User</a></li>
+<li>Top level <i>&lt;module&gt;</i>.gwt.xml <i><strong>inherits</strong></i> <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/User.gwt.xml">com.google.gwt.user.User</a></li>
 
-<li><a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/User.gwt.xml">com/google/gwt/user/User.gwt.xml</a>
-<i><strong>inherits</strong></i> <a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/Popup.gwt.xml">com.google.gwt.user.Popup</a></li>
+<li><a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/User.gwt.xml">com/google/gwt/user/User.gwt.xml</a>
+<i><strong>inherits</strong></i> <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/Popup.gwt.xml">com.google.gwt.user.Popup</a></li>
 
-<li><a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/Popup.gwt.xml">com/google/gwt/user/Popup.gwt.xml</a>
+<li><a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/Popup.gwt.xml">com/google/gwt/user/Popup.gwt.xml</a>
 <i><strong>contains</strong></i> <tt>&lt;replace-with&gt;</tt> elements to define deferred binding rules for the <a href="/javadoc/latest/com/google/gwt/user/client/ui/PopupPanel.html">PopupPanel</a> class.</li>
 </ul>
 
@@ -165,12 +165,12 @@
 hierarchy for the <tt>RemoteService</tt> class - used for GWT-RPC:</p>
 
 <ul>
-<li>Top level <i>&lt;module&gt;</i>.gwt.xml <i><strong>inherits</strong></i> <a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/User.gwt.xml">com.google.gwt.user.User</a></li>
+<li>Top level <i>&lt;module&gt;</i>.gwt.xml <i><strong>inherits</strong></i> <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/User.gwt.xml">com.google.gwt.user.User</a></li>
 
-<li><a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/User.gwt.xml">com/google/gwt/user/User.gwt.xml</a>
-<i><strong>inherits</strong></i> <a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/RemoteService.gwt.xml">com.googl.gwt.user.RemoteService</a></li>
+<li><a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/User.gwt.xml">com/google/gwt/user/User.gwt.xml</a>
+<i><strong>inherits</strong></i> <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/RemoteService.gwt.xml">com.googl.gwt.user.RemoteService</a></li>
 
-<li><a href="http://google-web-toolkit.googlecode.com/svn/releases/2.5/user/src/com/google/gwt/user/RemoteService.gwt.xml">com/google/gwt/user/RemoteService.gwt.xml</a>
+<li><a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/RemoteService.gwt.xml">com/google/gwt/user/RemoteService.gwt.xml</a>
 <i><strong>contains</strong></i> <tt>&lt;generates-with&gt;</tt> elements to define deferred binding rules for the <tt>RemoteService</tt> class.</li>
 </ul>
 
@@ -193,7 +193,7 @@
 &lt;/module&gt;
 </pre>
 
-<p>These directives instruct the GWT compiler to invoke methods in a <a href="/javadoc/latest/com/google/gwt/core/ext/Generator.html">Generator</a> subclass (<tt>ServiceInterfaceProxyGenerator</tt>) in order to generate special code when the deferred binding mechanism <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/GWT.html#create(java.lang.Class)">GWT.create()</a> is encountered while
+<p>These directives instruct the GWT compiler to invoke methods in a <a href="/javadoc/latest/com/google/gwt/core/ext/Generator.html">Generator</a> subclass (<tt>ServiceInterfaceProxyGenerator</tt>) in order to generate special code when the deferred binding mechanism <a href="/javadoc/latest/com/google/gwt/core/client/GWT.html#create(java.lang.Class)">GWT.create()</a> is encountered while
 compiling. In this case, if the <a href="/javadoc/latest/com/google/gwt/core/client/GWT.html#create(java.lang.Class)">GWT.create()</a> call references an instance of <tt>RemoteService</tt> or one of its subclasses, the <tt>ServiceInterfaceProxyGenerator</tt>'s generate() method
 will be invoked.</p>
 
diff --git a/src/main/markdown/doc/latest/DevGuideCodingBasicsFormatting.md b/src/main/markdown/doc/latest/DevGuideCodingBasicsFormatting.md
index 175a694..8fd7fab 100644
--- a/src/main/markdown/doc/latest/DevGuideCodingBasicsFormatting.md
+++ b/src/main/markdown/doc/latest/DevGuideCodingBasicsFormatting.md
@@ -1,5 +1,5 @@
 <p>GWT does not provide full emulation for the date and number formatting classes (java.text.DateFormat, java.text.DecimalFormat, java.text.NumberFormat, java.TimeFormat, et
-cetera). Instead, a subset of the functionality of the JRE classes is provided by <a href="/javadoc/latest/com/google/gwt/i18n/client/NumberFormat.html">com.google.gwt.i18n.client.NumberFormat</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/DateTimeFormat.html">com.google.gwt.i18n.client.DateTimeFormat</a>.</p>
+cetera). Instead, a subset of the functionality of the JRE classes is provided by <a href="/javadoc/latest/com/google/gwt/i18n/client/NumberFormat.html">com.google.gwt.i18n.client.NumberFormat</a> and <a href="/javadoc/latest/com/google/gwt/i18n/client/DateTimeFormat.html">com.google.gwt.i18n.client.DateTimeFormat</a>.</p>
 
 <p>The major difference between the standard Java classes and the GWT classes is the ability to switch between different locales for formating dates and numbers at runtime. In
 GWT, the <a href="DevGuideCodingBasics.html#DevGuideDeferredBinding">deferred binding</a> mechanism is used to load only the logic needed for the current locale into the
diff --git a/src/main/markdown/doc/latest/DevGuideCodingBasicsHistory.md b/src/main/markdown/doc/latest/DevGuideCodingBasicsHistory.md
index adf0756..2a470dd 100644
--- a/src/main/markdown/doc/latest/DevGuideCodingBasicsHistory.md
+++ b/src/main/markdown/doc/latest/DevGuideCodingBasicsHistory.md
@@ -61,7 +61,7 @@
 <ul>
 <li>Add a history token to the history stack when you want to enable a history event.</li>
 
-<li>Create an object that implements the <a href="/javadoc/latest/com/google/gwt/event/logical/shared/ValueChangeHandler.html">ValueChangeHandler</a> interface, parses the new token (available by calling <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/event/logical/shared/ValueChangeEvent.html#getValue()">ValueChangeEvent.getValue()</a>) and changes the application state to match.</li>
+<li>Create an object that implements the <a href="/javadoc/latest/com/google/gwt/event/logical/shared/ValueChangeHandler.html">ValueChangeHandler</a> interface, parses the new token (available by calling <a href="/javadoc/latest/com/google/gwt/event/logical/shared/ValueChangeEvent.html#getValue()">ValueChangeEvent.getValue()</a>) and changes the application state to match.</li>
 </ul>
 
 <p>The following short example shows how to add a history event each time the user selects a new tab in a <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabPanel.html">TabPanel</a>.</p>
diff --git a/src/main/markdown/doc/latest/DevGuideCodingBasicsJSNI.md b/src/main/markdown/doc/latest/DevGuideCodingBasicsJSNI.md
index 97063e5..8ebf6bf 100644
--- a/src/main/markdown/doc/latest/DevGuideCodingBasicsJSNI.md
+++ b/src/main/markdown/doc/latest/DevGuideCodingBasicsJSNI.md
@@ -398,7 +398,7 @@
 <p/>
 
 <ul>
-<li>Although Java arrays are not directly usable in JavaScript, there are some helper classes that efficiently achieve a similar effect: <a href="/javadoc/latest/com/google/gwt/core/client/JsArray.html">JsArray</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/JsArrayBoolean.html">JsArrayBoolean</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/JsArrayInteger.html">JsArrayInteger</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/JsArrayNumber.html">JsArrayNumber</a>, and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/JsArrayString.html">JsArrayString</a>. These classes are wrappers around a native JavaScript array.</li>
+<li>Although Java arrays are not directly usable in JavaScript, there are some helper classes that efficiently achieve a similar effect: <a href="/javadoc/latest/com/google/gwt/core/client/JsArray.html">JsArray</a>, <a href="/javadoc/latest/com/google/gwt/core/client/JsArrayBoolean.html">JsArrayBoolean</a>, <a href="/javadoc/latest/com/google/gwt/core/client/JsArrayInteger.html">JsArrayInteger</a>, <a href="/javadoc/latest/com/google/gwt/core/client/JsArrayNumber.html">JsArrayNumber</a>, and <a href="/javadoc/latest/com/google/gwt/core/client/JsArrayString.html">JsArrayString</a>. These classes are wrappers around a native JavaScript array.</li>
 </ul>
 
 
diff --git a/src/main/markdown/doc/latest/DevGuideCodingBasicsXML.md b/src/main/markdown/doc/latest/DevGuideCodingBasicsXML.md
index 6b5be28..abaea7d 100644
--- a/src/main/markdown/doc/latest/DevGuideCodingBasicsXML.md
+++ b/src/main/markdown/doc/latest/DevGuideCodingBasicsXML.md
@@ -63,7 +63,7 @@
 
 <p>The first step is to parse the raw XML text into an <a href="http://www.w3schools.com/dom/default.asp">XML DOM</a> structure we can use to navigate the data.
 GWT's XML parser is contained in the <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html">XMLParser</a>
-class. Call its <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html#parse(java.lang.String)">parse(String)</a> static method to parse the XML and return a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Document.html">Document</a> object. If an error occurs during parsing (for
+class. Call its <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html#parse(java.lang.String)">parse(String)</a> static method to parse the XML and return a <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html">Document</a> object. If an error occurs during parsing (for
 example, if the XML is not <a href="http://en.wikipedia.org/wiki/Well-formed_XML_document">well-formed</a>), the XMLParser will throw a <a href="/javadoc/latest/com/google/gwt/xml/client/DOMException.html">DOMException</a>.</p>
 
 <p>If parsing succeeds, the Document object we receive represents the XML document in memory. It is a tree composed of generic <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> objects. A node in the XML DOM is the basic unit of
@@ -93,7 +93,7 @@
 a complete list of types that derive from Node.</p>
 
 <p>To get to the DOM nodes from the Document object, we can use one of three methods. The <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html#getDocumentElement()">getDocumentElement()</a> method
-retrieves the <i>document element</i> (the top element at the root of the DOM tree) as an <a href="/javadoc/latest/com/google/gwt/xml/client/Element.html">Element</a>. We can then use the navigation methods of the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> class from which Element derives (e.g., <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#getChildNodes()">getChildNodes()</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#getNextSibling()">getNextSibling()</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#getParentNode()">getParentNode()</a>, etc.) to drill down and
+retrieves the <i>document element</i> (the top element at the root of the DOM tree) as an <a href="/javadoc/latest/com/google/gwt/xml/client/Element.html">Element</a>. We can then use the navigation methods of the <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> class from which Element derives (e.g., <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#getChildNodes()">getChildNodes()</a>, <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#getNextSibling()">getNextSibling()</a>, <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#getParentNode()">getParentNode()</a>, etc.) to drill down and
 retrieve the data we need.</p>
 
 <p>We can also go directly to a particular node or list of nodes using the <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html#getElementById(java.lang.String)">getElementById(String)</a>
@@ -105,11 +105,11 @@
 <p>In the example code, we use the getElementsByTagName(String) method to retrieve the necessary elements from the XML containing the email message. The sender's name is stored as
 an attribute of the <tt>&lt;from&gt;</tt> tag, so we use <a href="/javadoc/latest/com/google/gwt/xml/client/Element.html#getAttribute(java.lang.String)">getAttribute(String)</a>. The
 subject line is stored as text inside the <tt>&lt;subject&gt;</tt> tag, so we first find the subject element, and then retrieve its first (and only) child node and call <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#getNodeValue()">getNodeValue()</a> on it to get the text.
-Finally, the message body is stored in the same way (text within the <tt>&lt;body&gt;</tt> tag), but this time we explicitly cast the <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> to a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Text.html">Text</a> object and extract the text using <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/CharacterData.html#getData()">getData()</a>.</p>
+Finally, the message body is stored in the same way (text within the <tt>&lt;body&gt;</tt> tag), but this time we explicitly cast the <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> to a <a href="/javadoc/latest/com/google/gwt/xml/client/Text.html">Text</a> object and extract the text using <a href="/javadoc/latest/com/google/gwt/xml/client/CharacterData.html#getData()">getData()</a>.</p>
 
 <h2 id="building">Building an XML document</h2>
 
-<p>In addition to parsing existing documents, the GWT XML types can also be used to create and modify XML. To create a new XML document, call the static <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html#createDocument()">createDocument()</a> method of the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/XMLParser.html">XMLParser</a> class. You can then use the methods of the
-resulting <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html">Document</a> to <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Document.html#createElement(java.lang.String)">create elements</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Document.html#createTextNode(java.lang.String)">text nodes</a>, and other XML nodes. These nodes can be added to the DOM tree using the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#appendChild(com.google.gwt.xml.client.Node)">appendChild(Node)</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#insertBefore(com.google.gwt.xml.client.Node,%20com.google.gwt.xml.client.Node)">insertBefore(Node, Node)</a> methods. <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> also has methods for replacing and removing child nodes (<a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#replaceChild(com.google.gwt.xml.client.Node,%20com.google.gwt.xml.client.Node)">replaceChild(Node, Node)</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/xml/client/Node.html#removeChild(com.google.gwt.xml.client.Node)">removeChild(Node)</a>, respectively).</p>
+<p>In addition to parsing existing documents, the GWT XML types can also be used to create and modify XML. To create a new XML document, call the static <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html#createDocument()">createDocument()</a> method of the <a href="/javadoc/latest/com/google/gwt/xml/client/XMLParser.html">XMLParser</a> class. You can then use the methods of the
+resulting <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html">Document</a> to <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html#createElement(java.lang.String)">create elements</a>, <a href="/javadoc/latest/com/google/gwt/xml/client/Document.html#createTextNode(java.lang.String)">text nodes</a>, and other XML nodes. These nodes can be added to the DOM tree using the <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#appendChild(com.google.gwt.xml.client.Node)">appendChild(Node)</a> and <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#insertBefore(com.google.gwt.xml.client.Node,%20com.google.gwt.xml.client.Node)">insertBefore(Node, Node)</a> methods. <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html">Node</a> also has methods for replacing and removing child nodes (<a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#replaceChild(com.google.gwt.xml.client.Node,%20com.google.gwt.xml.client.Node)">replaceChild(Node, Node)</a> and <a href="/javadoc/latest/com/google/gwt/xml/client/Node.html#removeChild(com.google.gwt.xml.client.Node)">removeChild(Node)</a>, respectively).</p>
 
 
diff --git a/src/main/markdown/doc/latest/DevGuideCompilingAndDebugging.md b/src/main/markdown/doc/latest/DevGuideCompilingAndDebugging.md
index 6680ecc..49e74eb 100644
--- a/src/main/markdown/doc/latest/DevGuideCompilingAndDebugging.md
+++ b/src/main/markdown/doc/latest/DevGuideCompilingAndDebugging.md
@@ -355,27 +355,28 @@
 <pre>
 $ java -cp gwt-dev.jar com.google.gwt.dev.DevMode
 Missing required argument 'module[s]'
-<b>Google Web Toolkit 2.5.1</b>
-DevMode [-noserver] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort port-number | "auto"] [-server servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] [-extra dir] [-workDir dir] module[s]
+<b>Google Web Toolkit 2.6.1</b>
+DevMode [-[no]startServer] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort port-number | "auto"] [-server servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] [-extra dir] [-workDir dir] [-sourceLevel [auto, 1.6, 1.7]] module[s] 
 
 where 
-  -noserver        Prevents the embedded web server from running
-  -port            Specifies the TCP port for the embedded web server (defaults to 8888)
-  -whitelist       Allows the user to browse URLs that match the specified regexes (comma or space separated)
-  -blacklist       Prevents the user browsing URLs that match the specified regexes (comma or space separated)
-  -logdir          Logs to a file in the given directory, as well as graphically
-  -logLevel        The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
-  -gen             Debugging: causes normally-transient generated types to be saved in the specified directory
-  -bindAddress     Specifies the bind address for the code server and web server (defaults to 127.0.0.1)
-  -codeServerPort  Specifies the TCP port for the code server (defaults to 9997)
-  -server          Specify a different embedded web server to run (must implement ServletContainerLauncher)
-  -startupUrl      Automatically launches the specified URL
-  -war             The directory into which deployable output files will be written (defaults to 'war')
-  -deploy          The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
-  -extra           The directory into which extra files, not intended for deployment, will be written
-  -workDir         The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
+  -[no]startServer  Starts a servlet container serving the directory specified by the -war flag. (defaults to ON)
+  -port             Specifies the TCP port for the embedded web server (defaults to 8888)
+  -whitelist        Allows the user to browse URLs that match the specified regexes (comma or space separated)
+  -blacklist        Prevents the user browsing URLs that match the specified regexes (comma or space separated)
+  -logdir           Logs to a file in the given directory, as well as graphically
+  -logLevel         The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
+  -gen              Debugging: causes normally-transient generated types to be saved in the specified directory
+  -bindAddress      Specifies the bind address for the code server and web server (defaults to 127.0.0.1)
+  -codeServerPort   Specifies the TCP port for the code server (defaults to 9997)
+  -server           Specify a different embedded web server to run (must implement ServletContainerLauncher)
+  -startupUrl       Automatically launches the specified URL
+  -war              The directory into which deployable output files will be written (defaults to 'war')
+  -deploy           The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
+  -extra            The directory into which extra files, not intended for deployment, will be written
+  -workDir          The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
+  -sourceLevel      Specifies Java source level (defaults to auto:1.7)
 and 
-  module[s]        Specifies the name(s) of the module(s) to host
+  module[s]         Specifies the name(s) of the module(s) to host
 </pre>
 
 
@@ -454,7 +455,7 @@
 
 
 <pre>
-C:\gwt-2.0.0\samples\Hello&gt;ant
+C:\gwt-2.6.1\samples\Hello&gt;ant
 Buildfile: build.xml
 
 libs:
@@ -479,7 +480,7 @@
 <p>After running the GWT compiler your war directory should look something like this:</p>
 
 <pre>
-C:\gwt-2.0.0\samples\Hello&gt;\bin\find war
+C:\gwt-2.6.1\samples\Hello&gt;\bin\find war
 war
 war\hello
 war\hello\18EEC2DA45CB5F0C2050E2539AE61FCE.cache.html
@@ -583,31 +584,35 @@
 <pre>
 java -cp gwt-dev.jar com.google.gwt.dev.Compiler
 Missing required argument 'module[s]'
-<b>Google Web Toolkit 2.5.1</b>
-Compiler [-logLevel level] [-workDir dir] [-gen dir] [-style style] [-ea] [-XdisableClassMetadata] [-XdisableCastChecking] [-validateOnly] [-draftCompile] [-optimize level] [-compileReport] [-strict] [-XenableClosureCompiler] [-XfragmentMerge numFragments] [-XfragmentCount numFragments] [-localWorkers count] [-war dir] [-deploy dir] [-extra dir] module[s]
+<b>Google Web Toolkit 2.6.1</b>
+Compiler [-logLevel level] [-workDir dir] [-[no]compileReport] [-X[no]checkCasts] [-X[no]classMetadata] [-[no]draftCompile] [-[no]checkAssertions] [-X[no]closureCompiler] [-XfragmentCount numFragments] [-XfragmentMerge numFragments] [-gen dir] [-optimize level] [-[no]saveSource] [-style style] [-[no]failOnError] [-X[no]enforceStrictResources] [-[no]validateOnly] [-sourceLevel [auto, 1.6, 1.7]] [-localWorkers count] [-war dir] [-deploy dir] [-extra dir] [-saveSourceOutput dir] module[s] 
 
 where 
-  -logLevel                The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
-  -workDir                 The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
-  -gen                     Debugging: causes normally-transient generated types to be saved in the specified directory
-  -style                   Script output style: OBF[USCATED], PRETTY, or DETAILED (defaults to OBF)
-  -ea                      Debugging: causes the compiled output to check assert statements
-  -XdisableClassMetadata   EXPERIMENTAL: Disables some java.lang.Class methods (e.g. getName())
-  -XdisableCastChecking    EXPERIMENTAL: Disables run-time checking of cast operations
-  -validateOnly            Validate all source code, but do not compile
-  -draftCompile            Enable faster, but less-optimized, compilations
-  -optimize                Sets the optimization level used by the compiler.  0=none 9=maximum.
-  -compileReport           Create a compile report that tells the Story of Your Compile
-  -strict                  Only succeed if no input files have errors
-  -XenableClosureCompiler  EXPERIMENTAL: Enables Closure Compiler optimizations
-  -XfragmentMerge          DEPRECATED (use -XfragmentCount instead): Enables Fragment merging code splitter.
-  -XfragmentCount          EXPERIMENTAL: Limits of number of fragments using a code splitter that merges split points.
-  -localWorkers            The number of local workers to use when compiling permutations
-  -war                     The directory into which deployable output files will be written (defaults to 'war')
-  -deploy                  The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
-  -extra                   The directory into which extra files, not intended for deployment, will be written
+  -logLevel                     The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
+  -workDir                      The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
+  -[no]compileReport            Compile a report that tells the "Story of Your Compile". (defaults to OFF)
+  -X[no]checkCasts              EXPERIMENTAL: Insert run-time checking of cast operations. (defaults to ON)
+  -X[no]classMetadata           EXPERIMENTAL: Include metadata for some java.lang.Class methods (e.g. getName()). (defaults to ON)
+  -[no]draftCompile             Compile quickly with minimal optimizations. (defaults to OFF)
+  -[no]checkAssertions          Include assert statements in compiled output. (defaults to OFF)
+  -X[no]closureCompiler         EXPERIMENTAL: Compile output Javascript with the Closure compiler for even further optimizations. (defaults to OFF)
+  -XfragmentCount               EXPERIMENTAL: Limits of number of fragments using a code splitter that merges split points.
+  -XfragmentMerge               DEPRECATED (use -XfragmentCount instead): Enables Fragment merging code splitter.
+  -gen                          Debugging: causes normally-transient generated types to be saved in the specified directory
+  -optimize                     Sets the optimization level used by the compiler.  0=none 9=maximum.
+  -[no]saveSource               Enables saving source code needed by debuggers. Also see -debugDir. (defaults to OFF)
+  -style                        Script output style: OBF[USCATED], PRETTY, or DETAILED (defaults to OBF)
+  -[no]failOnError              Fail compilation if any input file contains an error. (defaults to OFF)
+  -X[no]enforceStrictResources  EXPERIMENTAL: Avoid adding implicit dependencies on "client" and "public" for modules that don't define any dependencies. (defaults to OFF)
+  -[no]validateOnly             Validate all source code, but do not compile. (defaults to OFF)
+  -sourceLevel                  Specifies Java source level (defaults to auto:1.7)
+  -localWorkers                 The number of local workers to use when compiling permutations
+  -war                          The directory into which deployable output files will be written (defaults to 'war')
+  -deploy                       The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
+  -extra                        The directory into which extra files, not intended for deployment, will be written
+  -saveSourceOutput             Overrides where source files useful to debuggers will be written. Default: saved with extras.
 and 
-  module[s]                Specifies the name(s) of the module(s) to compile
+  module[s]                     Specifies the name(s) of the module(s) to compile
 </pre>
 
 
diff --git a/src/main/markdown/doc/latest/DevGuideDeploying.md b/src/main/markdown/doc/latest/DevGuideDeploying.md
index 3ad13b0..360688f 100644
--- a/src/main/markdown/doc/latest/DevGuideDeploying.md
+++ b/src/main/markdown/doc/latest/DevGuideDeploying.md
@@ -15,7 +15,7 @@
 and <a
 href="DevGuideCodingBasics.html#DevGuideJSON">working with JSON data</a>, server-side scripts that receive and parse HTTP requests sent through the GWT <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html">RequestBuilder</a>, or GWT RPC (see <a href="#DevGuideDeployingServletContainerUsingRPC">&quot;Deploying on a servlet container using RPC&quot;</a> section below).
 
-<p>For an example of deploying GWT application files to a web server, suppose you want to deploy the <a href="http://gwt.google.com/samples/DynaTable/DynaTable.html">DynaTable</a> application on a web server, serving files from <code>/web/apps/dynatable_app/</code>. Once you've run the GWT compiler and generated the output in the <code>war/dynatable</code> directory, all you need to do is copy the host HTML page and stylesheet over to <code>web/apps/dynatable_app/</code> and copy the contents of the <code>war/dynatable</code> subdirectory to <code>/web/apps/dynatable_app/dynatable/</code>. At this point, the application is deployed. However, there are a few important points to keep in mind to make sure your application is properly deployed:</p>
+<p>For an example of deploying GWT application files to a web server, suppose you want to deploy the DynaTable application on a web server, serving files from <code>/web/apps/dynatable_app/</code>. Once you've run the GWT compiler and generated the output in the <code>war/dynatable</code> directory, all you need to do is copy the host HTML page and stylesheet over to <code>web/apps/dynatable_app/</code> and copy the contents of the <code>war/dynatable</code> subdirectory to <code>/web/apps/dynatable_app/dynatable/</code>. At this point, the application is deployed. However, there are a few important points to keep in mind to make sure your application is properly deployed:</p>
 
 <p></p>
 <ul>
@@ -30,7 +30,7 @@
 
 <p>Deploying a GWT application on a servlet container is also an easy process. Since the GWT compiler generates output in a directory structure that is already compliant to the <a href="http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html">Servlet 2.5 API specification</a>, you can deploy your application from the output directory itself. It would be better practice to copy the output and deploy it to a separate directory on your servlet container, however.</p>
 
-<p>Referring to the <a href="http://gwt.google.com/samples/DynaTable/DynaTable.html">DynaTable</a> sample, deploying your project would involve copying the GWT compiler output to the following path on your servlet container:</p>
+<p>Referring to the DynaTable sample, deploying your project would involve copying the GWT compiler output to the following path on your servlet container:</p>
 
 <pre class="prettyprint">
 webapps/dynatable/DynaTable.html
diff --git a/src/main/markdown/doc/latest/DevGuideI18n.md b/src/main/markdown/doc/latest/DevGuideI18n.md
index 373a5d4..42644e5 100644
--- a/src/main/markdown/doc/latest/DevGuideI18n.md
+++ b/src/main/markdown/doc/latest/DevGuideI18n.md
@@ -50,7 +50,7 @@
 
 <ul>
 <li><strong>Do you have existing localized properties files you'd like to reuse?</strong><br/>
-The i18nCreator tool can automatically generate interfaces that extend either <a href="/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/ConstantsWithLookup.html">ConstantsWithLookup</a> or <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/Messages.html">Messages</a>.</li>
+The i18nCreator tool can automatically generate interfaces that extend either <a href="/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a>, <a href="/javadoc/latest/com/google/gwt/i18n/client/ConstantsWithLookup.html">ConstantsWithLookup</a> or <a href="/javadoc/latest/com/google/gwt/i18n/client/Messages.html">Messages</a>.</li>
 </ul>
 
 <ul>
@@ -114,7 +114,7 @@
 </ul>
 
 <ul>
-<li><a href="/javadoc/latest/com/google/gwt/i18n/client/ConstantsWithLookup.html">ConstantsWithLookup</a> Like <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a> but with extra lookup flexibility for highly
+<li><a href="/javadoc/latest/com/google/gwt/i18n/client/ConstantsWithLookup.html">ConstantsWithLookup</a> Like <a href="/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a> but with extra lookup flexibility for highly
 data-driven applications</li>
 </ul>
 
@@ -386,7 +386,7 @@
 
 <p/>
 
-<p>Both <a href="/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/Messages.html">Messages</a> use traditional Java properties files, with
+<p>Both <a href="/javadoc/latest/com/google/gwt/i18n/client/Constants.html">Constants</a> and <a href="/javadoc/latest/com/google/gwt/i18n/client/Messages.html">Messages</a> use traditional Java properties files, with
 one notable difference: properties files used with GWT should be encoded as UTF-8 and may contain Unicode characters directly, avoiding the need for <tt>native2ascii</tt>. See the
 API documentation for the above interfaces for examples and formatting details. Many thanks to the <a href="http://tapestry.apache.org/">Tapestry</a> project for
 solving the problem of reading UTF-8 properties files in Tapestry's <tt>LocalizedProperties</tt> class.</p>
diff --git a/src/main/markdown/doc/latest/DevGuideI18nLocale.md b/src/main/markdown/doc/latest/DevGuideI18nLocale.md
index 927dfc1..a9e52d9 100644
--- a/src/main/markdown/doc/latest/DevGuideI18nLocale.md
+++ b/src/main/markdown/doc/latest/DevGuideI18nLocale.md
@@ -135,7 +135,7 @@
 XML</a> file, and all locales that GWT knows about that inherit from
 your compile-time locale will be automatically included.  You can see the
 result in the <a
-href="http://gwt.google.com/samples/Showcase/Showcase.html"><tt>Showcase</tt>
+href="http://samples.gwtproject.org/samples/Showcase/Showcase.html"><tt>Showcase</tt>
 sample application</a>.</p>
 
 <h3>Caveats</h3>
@@ -146,7 +146,7 @@
  to be included in the selection script, so inheritance won't work properly
  in all cases.  This means you either need to specifically control the set
  of possible locales, such as in the locale selector in the <a
-href="http://gwt.google.com/samples/Showcase/Showcase.html"><tt>Showcase</tt>
+href="http://samples.gwtproject.org/samples/Showcase/Showcase.html"><tt>Showcase</tt>
 sample application</a>, or have the server choose the locale using the
 proper inheritance tables (<tt>GwtLocaleFactoryImpl</tt> will be helpful here,
 and you will need a way to get the set of locales your application was built
@@ -163,8 +163,8 @@
 
 <p>A property provider is specified in the <a href="DevGuideOrganizingProjects.html#DevGuideModuleXml">module XML file</a> as a JavaScript fragment that will return the value for the
 named property at runtime. In this case, you would want to define the locale property using a property provider. To see examples of <tt>&lt;property-provider&gt;</tt> definitions
-in action, see the files <a href="http://code.google.com/p/google-web-toolkit/source/browse/releases/2.5/user/src/com/google/gwt/i18n/I18N.gwt.xml">I18N.gwt.xml</a> and
-<a href="http://code.google.com/p/google-web-toolkit/source/browse/releases/2.5/user/src/com/google/gwt/user/UserAgent.gwt.xml">UserAgent.gwt.xml</a> in the GWT source code.</p>
+in action, see the files <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/i18n/I18N.gwt.xml">I18N.gwt.xml</a> and
+<a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/UserAgent.gwt.xml">UserAgent.gwt.xml</a> in the GWT source code.</p>
 
 <h2 id="LocaleInfo">Programmatic Access to Locale Information</h2>
 
diff --git a/src/main/markdown/doc/latest/DevGuideLogging.md b/src/main/markdown/doc/latest/DevGuideLogging.md
index 67c0f29..ca8aff7 100644
--- a/src/main/markdown/doc/latest/DevGuideLogging.md
+++ b/src/main/markdown/doc/latest/DevGuideLogging.md
@@ -59,8 +59,8 @@
 </p>
 
 <p>
-LogExample is configured using <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/LogExample.gwt.xml"><code>LogExample.gwt.xml</code></a>.
-The entry point for the app is <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java"><code>LogExample.java</code></a> &mdash; it simply creates and adds the various demo modules to the page.  Each of these modules illustrates a different set of logging concepts; this tutorial will walk you through them.
+LogExample is configured using <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/LogExample.gwt.xml"><code>LogExample.gwt.xml</code></a>.
+The entry point for the app is <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java"><code>LogExample.java</code></a> &mdash; it simply creates and adds the various demo modules to the page.  Each of these modules illustrates a different set of logging concepts; this tutorial will walk you through them.
 </p>
 
 
@@ -75,10 +75,10 @@
 </p>
 
 <p>
- If you open <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java"><code>LogExample.java</code></a> you can see that we've created 3 loggers:
+ If you open <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java"><code>LogExample.java</code></a> you can see that we've created 3 loggers:
 </p>
 
-<pre class="prettyprint">// <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java">LogExample.java</a>
+<pre class="prettyprint">// <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/LogExample.java">LogExample.java</a>
 
   private static Logger childLogger = Logger.getLogger("ParentLogger.Child");
   private static Logger parentLogger = Logger.getLogger("ParentLogger");
@@ -86,11 +86,11 @@
 </pre>
 
 <p>
-We've passed these 3 loggers into <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/LoggerController.java"><code>LoggerController</code></a>, which in turn, creates an instance of
-<a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/OneLoggerController.java"><code>OneLoggerController</code></a> for each of them.  In <code>OneLoggerController.java</code> you can see example code for changing the Level of the logger, logging to the logger, and logging an exception to the logger.
+We've passed these 3 loggers into <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/LoggerController.java"><code>LoggerController</code></a>, which in turn, creates an instance of
+<a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/OneLoggerController.java"><code>OneLoggerController</code></a> for each of them.  In <code>OneLoggerController.java</code> you can see example code for changing the Level of the logger, logging to the logger, and logging an exception to the logger.
 </p>
 
-<pre class="prettyprint">// <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/OneLoggerController.java">OneLoggerController</a>
+<pre class="prettyprint">// <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/OneLoggerController.java">OneLoggerController</a>
 
   // Change the level of the logger
   @UiHandler("levelTextBox")
@@ -164,7 +164,7 @@
 Here's an example of how a checkbox adds or removes a handler:
 </p>
 
-<pre class="prettyprint">// <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/HandlerController.java">HandlerController.java</a>
+<pre class="prettyprint">// <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/HandlerController.java">HandlerController.java</a>
 
     public void onValueChange(ValueChangeEvent<Boolean> event) {
       if (checkbox.getValue()) {
@@ -202,7 +202,7 @@
 of a <code>HasWidgetsLogHandler</code> and add that Handler to a logger.
 </p>
 
-<pre class="prettyprint">// <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/VerticalPanel.java">VerticalPanel.java</a>
+<pre class="prettyprint">// <a href="https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/user/client/ui/VerticalPanel.java">VerticalPanel.java</a>
 
     VerticalPanel customLogArea;
 
@@ -225,7 +225,7 @@
 </p>
 
 <p>
- In <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/ServerLoggingArea.java"><code>ServerLoggingArea.java</code></a>, you can experiment with these concepts.  The buttons in that section will trigger logging calls on the server, as well as logging calls in <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/shared/SharedClass.java"><code>SharedClass.java</code></a> from both the client and server side.  Note the slight differences in formatting between client-side and server-side logging, as well as the different handlers each is logged to (in the tutorial, server-side logging will simply log to stderr, while client-side logging will log to all of the Handlers discussed above).
+ In <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/ServerLoggingArea.java"><code>ServerLoggingArea.java</code></a>, you can experiment with these concepts.  The buttons in that section will trigger logging calls on the server, as well as logging calls in <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/shared/SharedClass.java"><code>SharedClass.java</code></a> from both the client and server side.  Note the slight differences in formatting between client-side and server-side logging, as well as the different handlers each is logged to (in the tutorial, server-side logging will simply log to stderr, while client-side logging will log to all of the Handlers discussed above).
 </p>
 
 <h2 id="Remote_Logging"> Remote Logging </h2>
@@ -235,7 +235,7 @@
 </p>
 
 <pre class="prettyprint">
-# <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/LogExample.gwt.xml">LogExample.gwt.xml</a>
+# <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/LogExample.gwt.xml">LogExample.gwt.xml</a>
 
   &lt;set-property name="gwt.logging.simpleRemoteHandler" value="ENABLED" /&gt;
 </pre>
@@ -262,7 +262,7 @@
 Code that normally compiles out will still be present in Development mode.  You can  use the same condition as above to hide code from Development Mode, as shown here:
 </p>
 
-<pre class="prettyprint">// <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/logexample/src/com/google/gwt/sample/logexample/client/CustomLogArea.java">VerticalPanel.java</a>
+<pre class="prettyprint">// <a href="https://gwt.googlesource.com/gwt/+/master/samples/logexample/src/com/google/gwt/sample/logexample/client/CustomLogArea.java">VerticalPanel.java</a>
 
     // Although this code will compile out without this check in web mode, the guard will ensure
     // that the handler does not show up in development mode.
diff --git a/src/main/markdown/doc/latest/DevGuideMvpActivitiesAndPlaces.md b/src/main/markdown/doc/latest/DevGuideMvpActivitiesAndPlaces.md
index b64818e..44a88a6 100644
--- a/src/main/markdown/doc/latest/DevGuideMvpActivitiesAndPlaces.md
+++ b/src/main/markdown/doc/latest/DevGuideMvpActivitiesAndPlaces.md
@@ -225,7 +225,7 @@
 
 <p>You can use &lt;when-property-is&gt; to specify different
 implementations based on user.agent, locale, or other properties you
-define. The <a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/mobilewebapp/">mobilewebapp</a>
+define. The <a href="https://gwt.googlesource.com/gwt/+/master/samples/mobilewebapp/">mobilewebapp</a>
 sample application defines a "formfactor" property used to 
 select a different view implementations for mobile, tablet, and desktop devices.</p>
 
diff --git a/src/main/markdown/doc/latest/DevGuideOrganizingProjects.md b/src/main/markdown/doc/latest/DevGuideOrganizingProjects.md
index 7016cfd..6692a68 100644
--- a/src/main/markdown/doc/latest/DevGuideOrganizingProjects.md
+++ b/src/main/markdown/doc/latest/DevGuideOrganizingProjects.md
@@ -355,7 +355,7 @@
 
 <h3>Entry-Point Classes</h3>
 
-<p>A module entry-point is any class that is assignable to <a href="/javadoc/latest/com/google/gwt/core/client/EntryPoint.html">EntryPoint</a> and that can be constructed without parameters. When a module is loaded, every entry point class is instantiated and its <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/core/client/EntryPoint.html#onModuleLoad()">EntryPoint.onModuleLoad()</a> method gets
+<p>A module entry-point is any class that is assignable to <a href="/javadoc/latest/com/google/gwt/core/client/EntryPoint.html">EntryPoint</a> and that can be constructed without parameters. When a module is loaded, every entry point class is instantiated and its <a href="/javadoc/latest/com/google/gwt/core/client/EntryPoint.html#onModuleLoad()">EntryPoint.onModuleLoad()</a> method gets
 called.</p>
 
 <h3>Source Path</h3>
diff --git a/src/main/markdown/doc/latest/DevGuideRequestFactory.md b/src/main/markdown/doc/latest/DevGuideRequestFactory.md
index 37002b8..45dc5f2 100644
--- a/src/main/markdown/doc/latest/DevGuideRequestFactory.md
+++ b/src/main/markdown/doc/latest/DevGuideRequestFactory.md
@@ -65,7 +65,7 @@
 entities are annotated with @Entity. RequestFactory does not require the use of
 any particular framework or annotations on your domain classes.  Here's part of
 an entity definition from the <a
-href="http://code.google.com/p/google-web-toolkit/source/browse/#svn/trunk/samples/expenses">Expenses
+href="https://gwt.googlesource.com/gwt/+/master/samples/expenses">Expenses
 sample application</a> found in the GWT distribution.</p>
 
 <pre class="prettyprint">
@@ -679,7 +679,7 @@
 
 <p>Changes to related entities can be persisted in a single request.
 For example, this code from the 
-<a href="http://code.google.com/p/google-web-toolkit/source/browse/#svn/trunk/samples/dynatablerf">DynatableRF sample app</a> in GWT trunk creates a new Person and Address at the same time:</p>
+<a href="https://gwt.googlesource.com/gwt/+/master/samples/dynatablerf">DynatableRF sample app</a> in GWT trunk creates a new Person and Address at the same time:</p>
 
 <pre class="prettyprint">
 PersonRequest context = requestFactory.personRequest();
diff --git a/src/main/markdown/doc/latest/DevGuideServerCommunication.md b/src/main/markdown/doc/latest/DevGuideServerCommunication.md
index f56404a..cab27a4 100644
--- a/src/main/markdown/doc/latest/DevGuideServerCommunication.md
+++ b/src/main/markdown/doc/latest/DevGuideServerCommunication.md
@@ -753,15 +753,15 @@
 </pre>
 
 <p><a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html">RequestBuilder</a> is the core class you'll
-need for constructing and sending HTTP requests. Its <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#RequestBuilder(com.google.gwt.http.client.RequestBuilder.Method,%20java.lang.String)">constructor</a> has parameters for specifying the HTTP method of the request (GET, POST, etc.) and the URL (the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/URL.html">URL</a> utility class is handy for escaping invalid characters).
-Once you have a RequestBuilder object, you can use its methods to set the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setUser(java.lang.String)">username</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setPassword(java.lang.String)">password</a>, and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setTimeoutMillis(int)">timeout interval</a>. You can
+need for constructing and sending HTTP requests. Its <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#RequestBuilder(com.google.gwt.http.client.RequestBuilder.Method,%20java.lang.String)">constructor</a> has parameters for specifying the HTTP method of the request (GET, POST, etc.) and the URL (the <a href="/javadoc/latest/com/google/gwt/http/client/URL.html">URL</a> utility class is handy for escaping invalid characters).
+Once you have a RequestBuilder object, you can use its methods to set the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setUser(java.lang.String)">username</a>, <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setPassword(java.lang.String)">password</a>, and <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setTimeoutMillis(int)">timeout interval</a>. You can
 also set any number of <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#setHeader(java.lang.String,%20java.lang.String)">headers</a> in the HTTP request.</p>
 
-<p>Once the HTTP request is ready, call the server using the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#sendRequest(java.lang.String,%20com.google.gwt.http.client.RequestCallback)">sendRequest(String, RequestCallback)</a> method. The <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/RequestCallback.html">RequestCallback</a> argument you pass will handle
-the response or the error that results. When a request completes normally, your <a href="/javadoc/latest/com/google/gwt/http/client/RequestCallback.html#onResponseReceived(com.google.gwt.http.client.Request,%20com.google.gwt.http.client.Response)">onResponseReceived(Request, Response)</a> method is invoked. Details of the response (for example, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/Response.html#getStatusCode()">status code</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/Response.html#getHeaders()">HTTP headers</a>, and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/Response.html#getText()">response text</a>) can be retrieved from the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/Response.html">Response</a> argument. Note that the
+<p>Once the HTTP request is ready, call the server using the <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#sendRequest(java.lang.String,%20com.google.gwt.http.client.RequestCallback)">sendRequest(String, RequestCallback)</a> method. The <a href="/javadoc/latest/com/google/gwt/http/client/RequestCallback.html">RequestCallback</a> argument you pass will handle
+the response or the error that results. When a request completes normally, your <a href="/javadoc/latest/com/google/gwt/http/client/RequestCallback.html#onResponseReceived(com.google.gwt.http.client.Request,%20com.google.gwt.http.client.Response)">onResponseReceived(Request, Response)</a> method is invoked. Details of the response (for example, <a href="/javadoc/latest/com/google/gwt/http/client/Response.html#getStatusCode()">status code</a>, <a href="/javadoc/latest/com/google/gwt/http/client/Response.html#getHeaders()">HTTP headers</a>, and <a href="/javadoc/latest/com/google/gwt/http/client/Response.html#getText()">response text</a>) can be retrieved from the <a href="/javadoc/latest/com/google/gwt/http/client/Response.html">Response</a> argument. Note that the
 onResponseReceived(Request, Response) method is called even if the HTTP status code is something other than 200 (success). If the call <i>does not</i> complete normally, the <a href="/javadoc/latest/com/google/gwt/http/client/RequestCallback.html#onError(com.google.gwt.http.client.Request,%20java.lang.Throwable)">onError(Request, Throwable)</a> method gets called, with the second parameter describing the type error that occurred.</p>
 
-<p>As noted before, all HTTP calls in GWT are asynchronous, so the code following the call to <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#sendRequest(java.lang.String,%20com.google.gwt.http.client.RequestCallback)">sendRequest(String, RequestCallback)</a> will be executed immediately, <i>not</i> after the server responds to the HTTP request. You can use the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/client/Request.html">Request</a> object that is returned from sendRequest(String,
+<p>As noted before, all HTTP calls in GWT are asynchronous, so the code following the call to <a href="/javadoc/latest/com/google/gwt/http/client/RequestBuilder.html#sendRequest(java.lang.String,%20com.google.gwt.http.client.RequestCallback)">sendRequest(String, RequestCallback)</a> will be executed immediately, <i>not</i> after the server responds to the HTTP request. You can use the <a href="/javadoc/latest/com/google/gwt/http/client/Request.html">Request</a> object that is returned from sendRequest(String,
 RequestCallback) to <a href="/javadoc/latest/com/google/gwt/http/client/Request.html#isPending()">monitor the status</a> of
 the call, and <a href="/javadoc/latest/com/google/gwt/http/client/Request.html#cancel()">cancel it</a> if necessary.</p>
 
diff --git a/src/main/markdown/doc/latest/DevGuideTesting.md b/src/main/markdown/doc/latest/DevGuideTesting.md
index e4c2702..542c5b6 100644
--- a/src/main/markdown/doc/latest/DevGuideTesting.md
+++ b/src/main/markdown/doc/latest/DevGuideTesting.md
@@ -280,7 +280,7 @@
 <p>GWT's <a href="http://www.junit.org">JUnit</a> integration provides special support for testing functionality that cannot be executed in straight-line code. For
 example, you might want to make an <a href="DevGuideServerCommunication.html#DevGuideRemoteProcedureCalls">RPC</a> call to a server and then validate the response. However, in a normal
 JUnit test run, the test stops as soon as the test method returns control to the caller, and GWT does not support multiple threads or blocking. To support this use case, <a href="/javadoc/latest/com/google/gwt/junit/client/GWTTestCase.html">GWTTestCase</a> has extended the <tt>TestCase</tt> API.
-The two key methods are <a href="/javadoc/latest/com/google/gwt/junit/client/GWTTestCase.html#delayTestFinish(int)">GWTTestCase.delayTestFinish(int)</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/junit/client/GWTTestCase.html#finishTest()">GWTTestCase.finishTest()</a>. Calling
+The two key methods are <a href="/javadoc/latest/com/google/gwt/junit/client/GWTTestCase.html#delayTestFinish(int)">GWTTestCase.delayTestFinish(int)</a> and <a href="/javadoc/latest/com/google/gwt/junit/client/GWTTestCase.html#finishTest()">GWTTestCase.finishTest()</a>. Calling
 <tt>delayTestFinish()</tt> during a test method's execution puts that test in asynchronous mode, which means the test will not finish when the test method returns control to the
 caller. Instead, a <i>delay period</i> begins, which lasts the amount of time specified in the call to <tt>delayTestFinish()</tt>. During the delay period, the test system will
 wait for one of three things to happen:</p>
diff --git a/src/main/markdown/doc/latest/DevGuideTestingRemoteTesting.md b/src/main/markdown/doc/latest/DevGuideTestingRemoteTesting.md
index 43cd590..a9b7221 100644
--- a/src/main/markdown/doc/latest/DevGuideTestingRemoteTesting.md
+++ b/src/main/markdown/doc/latest/DevGuideTestingRemoteTesting.md
@@ -55,7 +55,7 @@
 <p>If you are not familiar with <em>development</em> mode versus <em>production mode</em>, you should read the associated tutorials
 on <a href="DevGuideCompilingAndDebugging.html">Compiling and Debugging</a> first. All of the following examples assume that you are running
 tests in development mode, which requires that you have the
-<a href="http://gwt.google.com/missing-plugin/">GWT Developer Plugin</a> installed. Its important to note that URLs must be
+<a href="/missing-plugin/">GWT Developer Plugin</a> installed. Its important to note that URLs must be
 whitelisted before this plugin will connect to them.  <font color="red">This means that you must allow the remote connection on the remote
 system the first time you run the test, or ahead of time if possible.</font></p>
 
@@ -150,7 +150,7 @@
 
   <li>Install <a href="http://getfirebug.com/">Firebug</a> (useful for debugging) </li>
 
-  <li>Install the <a href="http://gwt.google.com/missing-plugin/">GWT Developer Plugin</a></li>
+  <li>Install the <a href="/missing-plugin/">GWT Developer Plugin</a></li>
 
   <li>Whitelist the hosts that will launch the development mode code server.  Since Selenium copies the
       profile for each test, you must do this now.  If you do not, you will have to allow the remote connection for every test!
diff --git a/src/main/markdown/doc/latest/DevGuideUi.md b/src/main/markdown/doc/latest/DevGuideUi.md
index 1e5d94d..0951aa2 100644
--- a/src/main/markdown/doc/latest/DevGuideUi.md
+++ b/src/main/markdown/doc/latest/DevGuideUi.md
@@ -1,6 +1,6 @@
 <p>GWT user interface classes are similar to those in existing UI frameworks such as <a href="http://java.sun.com/javase/6/docs/api/javax/swing/package-summary.html">Swing</a> and <a href="http://www.eclipse.org/swt/">SWT</a> except that the widgets are rendered using dynamically-created HTML rather than pixel-oriented graphics.   </p>
 
-<p>In traditional JavaScript programming, dynamic user interface creation is done by manipulating the browser's DOM. While GWT provides access to the browser's DOM directly using the <a href="/javadoc/latest/com/google/gwt/dom/client/package-summary.html">DOM package</a>, it is far easier to use classes from the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/Widget.html">Widget</a> hierarchy. The Widget classes make it easier to quickly build interfaces that will work correctly on all browsers. </p>
+<p>In traditional JavaScript programming, dynamic user interface creation is done by manipulating the browser's DOM. While GWT provides access to the browser's DOM directly using the <a href="/javadoc/latest/com/google/gwt/dom/client/package-summary.html">DOM package</a>, it is far easier to use classes from the <a href="/javadoc/latest/com/google/gwt/user/client/ui/Widget.html">Widget</a> hierarchy. The Widget classes make it easier to quickly build interfaces that will work correctly on all browsers. </p>
 
 <style type="text/css">
    ol.toc li { font-weight: normal; }
diff --git a/src/main/markdown/doc/latest/DevGuideUiBinder.md b/src/main/markdown/doc/latest/DevGuideUiBinder.md
index 38dcfab..7ced0ba 100644
--- a/src/main/markdown/doc/latest/DevGuideUiBinder.md
+++ b/src/main/markdown/doc/latest/DevGuideUiBinder.md
@@ -74,7 +74,7 @@
 <p class='note'>
 <strong>Quick start:</strong> If instead you want to jump right in to
 the code, take a peek
-at <a href="http://code.google.com/p/google-web-toolkit/source/detail?r=6192">this
+at <a href="https://gwt.googlesource.com/gwt/+/ee29b77c519e7fbdee1794b72a983715b398c27d%5E!/">this
 patch</a>. It includes the work to change the venerable Mail sample to
 use UiBinder. Look for pairs of files like Mail.java and Mail.ui.xml.
 </p>
@@ -474,7 +474,7 @@
 
 &lt;/ui:UiBinder></pre>
 
-<p>A <a href="/javadoc/latest/com/google/gwt/resources/client/CssResource.html">CssResource</a> interface is generated for you, along with a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/resources/client/ClientBundle.html">ClientBundle</a>. This means that the compiler will warn you if you misspell the class name when you try to use it (e.g. <tt>{style.prettty}</tt>). Also, your CSS class name will be obfuscated, thus protecting it from collision with like class names in other CSS blocks&mdash;no more global CSS namespace!  </p>
+<p>A <a href="/javadoc/latest/com/google/gwt/resources/client/CssResource.html">CssResource</a> interface is generated for you, along with a <a href="/javadoc/latest/com/google/gwt/resources/client/ClientBundle.html">ClientBundle</a>. This means that the compiler will warn you if you misspell the class name when you try to use it (e.g. <tt>{style.prettty}</tt>). Also, your CSS class name will be obfuscated, thus protecting it from collision with like class names in other CSS blocks&mdash;no more global CSS namespace!  </p>
 
 <p>In fact, you can take advantage of this within a single template: </p>
 
diff --git a/src/main/markdown/doc/latest/DevGuideUiCellTable.md b/src/main/markdown/doc/latest/DevGuideUiCellTable.md
index 162da64..9c0b3ab 100644
--- a/src/main/markdown/doc/latest/DevGuideUiCellTable.md
+++ b/src/main/markdown/doc/latest/DevGuideUiCellTable.md
@@ -10,7 +10,7 @@
 <p>
 A cell table (data presentation table) provides high-performance rendering of large data sets
 in a tabular view. You can check out the
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">Cell Table example</a>
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">Cell Table example</a>
 in the GWT Showcase to see it in action.
 </p>
 
diff --git a/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md b/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md
index 29c9194..054cfc3 100644
--- a/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md
+++ b/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md
@@ -1,9 +1,9 @@
 <p>
 Cell widgets (data presentation widgets) are high-performance, lightweight widgets composed of Cells for displaying data.
-Examples are <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">lists</a>,
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">tables</a>,
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTree">trees</a> and
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellBrowser">browsers</a>.
+Examples are <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">lists</a>,
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">tables</a>,
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTree">trees</a> and
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellBrowser">browsers</a>.
 These widgets are designed to handle and display very large sets of data quickly.
 A cell widget renders its user interface as an HTML string, using innerHTML instead of traditional DOM manipulation.
 This design follows the flyweight pattern where data is accessed and cached only as needed, and passed to
@@ -16,11 +16,11 @@
 </p>
 
 <p>
-For example, in the <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CellList example</a> of the Showcase, every selectable data record is rendered by a single Cell instance. Notice that the data that a single cell represents can be a composition of different data fields from the data source. In this example, the cell holds data of type ContactInfo, which represents a contact, including name, address and picture.
+For example, in the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CellList example</a> of the Showcase, every selectable data record is rendered by a single Cell instance. Notice that the data that a single cell represents can be a composition of different data fields from the data source. In this example, the cell holds data of type ContactInfo, which represents a contact, including name, address and picture.
 </p>
 
 <p>
-In the <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">CellTable example</a>, a different Cell is used to render each Column of a row.  The five columns in this example present data from a boolean and four strings.
+In the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">CellTable example</a>, a different Cell is used to render each Column of a row.  The five columns in this example present data from a boolean and four strings.
 </p>
 
 <ol style="list-style: none; margin-top: 12px;">
@@ -66,11 +66,11 @@
 This document describes or points to three kinds of code examples, so you can jump in at any level.
 <ul>
   <li><b>Live demos</b> - Visit the GWT Showcase for examples of widgets
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CellList</a>,
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">CellTable</a>,
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTree">CellTree</a>,
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellBrowser">CellBrowser</a>, plus examples of Cells in the 
-<a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellSampler">Cell Sampler</a>.
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CellList</a>,
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">CellTable</a>,
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTree">CellTree</a>,
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellBrowser">CellBrowser</a>, plus examples of Cells in the 
+<a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellSampler">Cell Sampler</a>.
 Note: The prefix "Cw" in showcase class names stands for "ContentWidget", the parent class of each Showcase example.</li>
   <li><b>Simplified examples</b> - The code examples displayed in-line throughout this documented are short, simplified examples, often pared-down versions of the real-world examples.</li>
   <li><b>Real-world examples</b> - Most of the cell widgets also have source code examples (.java files) at 
@@ -90,7 +90,7 @@
 
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a CellList&lt;ContactInfo&gt; (on the left). Each list item is a custom type ContactCell&lt;ContactInfo&gt;.  The right-hand widget is a normal Composite widget that renders the data for a selected contact.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a CellList&lt;ContactInfo&gt; (on the left). Each list item is a custom type ContactCell&lt;ContactInfo&gt;.  The right-hand widget is a normal Composite widget that renders the data for a selected contact.
 </p>
 
 
@@ -107,11 +107,11 @@
 </ol>
 
 <p>
-The data inserted in the last step is updated by the data provider (<a href="/javadoc/latest/com/google/gwt/view/client/ListDataProvider.html">ListDataProvider</a> or <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/view/client/AsyncDataProvider.html">AsyncDataProvider</a>).  If you need to allow the user to modify the content of a cell and update the database, use ValueUpdater instead of setRowData in the last step, as described in <a href="#updating-from-celllist">Updating a Database From a CellList</a>.
+The data inserted in the last step is updated by the data provider (<a href="/javadoc/latest/com/google/gwt/view/client/ListDataProvider.html">ListDataProvider</a> or <a href="/javadoc/latest/com/google/gwt/view/client/AsyncDataProvider.html">AsyncDataProvider</a>).  If you need to allow the user to modify the content of a cell and update the database, use ValueUpdater instead of setRowData in the last step, as described in <a href="#updating-from-celllist">Updating a Database From a CellList</a>.
 </p>
 
 <p>
-<b>Code Example</b> - The example below is available at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellListExample.java">CellListExample.java</a>
+<b>Code Example</b> - The example below is available at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellListExample.java">CellListExample.java</a>
 </p>
 
 <p>
@@ -167,7 +167,7 @@
 </p>
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> shows a CellTable&lt;ContactInfo&gt;. Each row item has 5 columns rendered respectively as a CheckboxCell, EditTextCell, EditTextCell, SelectionCell and TextCell.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> shows a CellTable&lt;ContactInfo&gt;. Each row item has 5 columns rendered respectively as a CheckboxCell, EditTextCell, EditTextCell, SelectionCell and TextCell.
 </p>
 
 <p>
@@ -184,7 +184,7 @@
 </ol>
 
 <p>
-The data inserted in the last step is updated by the data provider (<a href="/javadoc/latest/com/google/gwt/view/client/ListDataProvider.html">ListDataProvider</a> or <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/view/client/AsyncDataProvider.html">AsyncDataProvider</a>).  If you need to allow the user to modify the content of a cell and update the database, use FieldUpdater instead of setRowData in the last step, as described in <a href="#updating-from-celltable">Updating a Database From a CellTable</a>.
+The data inserted in the last step is updated by the data provider (<a href="/javadoc/latest/com/google/gwt/view/client/ListDataProvider.html">ListDataProvider</a> or <a href="/javadoc/latest/com/google/gwt/view/client/AsyncDataProvider.html">AsyncDataProvider</a>).  If you need to allow the user to modify the content of a cell and update the database, use FieldUpdater instead of setRowData in the last step, as described in <a href="#updating-from-celltable">Updating a Database From a CellTable</a>.
 </p>
 
 <p>
@@ -193,7 +193,7 @@
 </p>
 
 <p>
-<b>Code Example</b> - The example below is a pared-down version of <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellTableExample.java">CellTableExample.java</a>
+<b>Code Example</b> - The example below is a pared-down version of <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellTableExample.java">CellTableExample.java</a>
 </p>
 
 <pre class="prettyprint">
@@ -265,7 +265,7 @@
 <h2 id="celltree">Creating a CellTree</h2>
 
 <p>
-CellTree renders a hierarchy of nodes, such as this <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTree">CwCellTree</a>.  A node can be either a leaf node or have children.  Thus, a CellTree can have levels of nodes that go progressively deeper.  A node is represented by a NodeInfo, which contains all of the information needed to render a single node.
+CellTree renders a hierarchy of nodes, such as this <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTree">CwCellTree</a>.  A node can be either a leaf node or have children.  Thus, a CellTree can have levels of nodes that go progressively deeper.  A node is represented by a NodeInfo, which contains all of the information needed to render a single node.
 </p>
 
 <p>
@@ -281,7 +281,7 @@
 </p>
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTree">CwCellTree example</a> shows a CellTree.  It has three levels rendered respectively as custom types CategoryCell, LetterCountCell and ContactCell (the same type from the <a href="#celllist">CellList</a> demo).  The checkbox has an update method to select the ContactCell when checked.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTree">CwCellTree example</a> shows a CellTree.  It has three levels rendered respectively as custom types CategoryCell, LetterCountCell and ContactCell (the same type from the <a href="#celllist">CellList</a> demo).  The checkbox has an update method to select the ContactCell when checked.
 </p>
 
 <p>
@@ -289,7 +289,7 @@
 </p>
 
 <ol>
- <li>Define a <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html">TreeViewModel</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html#getNodeInfo(T)">getNodeInfo</a>
+ <li>Define a <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html">TreeViewModel</a> and <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html#getNodeInfo(T)">getNodeInfo</a>
     <ol style="list-style-type: lower-alpha">
       <li>In getNodeInfo, create a data provider for the child nodes.</li>
       <li>Populate the data provider with data.</li>
@@ -301,11 +301,11 @@
 </ol>
 
 <p>
-<b>Code Example #1</b> - The example below is a simplified example of CellTree, and is available at  <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellTreeExample.java">CellTreeExample.java</a>.
+<b>Code Example #1</b> - The example below is a simplified example of CellTree, and is available at  <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellTreeExample.java">CellTreeExample.java</a>.
 </p>
 
 <p>
-<b>Code Example #2</b> - For a real-world example of CellTree, see <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellTreeExample2.java">CellTreeExample2.java</a>.
+<b>Code Example #2</b> - For a real-world example of CellTree, see <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellTreeExample2.java">CellTreeExample2.java</a>.
 </p>
 
 <pre class="prettyprint">
@@ -352,7 +352,7 @@
 </pre>
 
 <p>
-When you instantiate a CellTree, you must pass in an instance of a concrete class that implements interface <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html">TreeViewModel</a>.  This concrete class gets and organizes the data into a hierarchy in the implementation of method getNodeInfo(value).  When a tree node is opened, the tree calls <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html#getNodeInfo(T)">getNodeInfo(value)</a> to get the data provider and Cell used to render the child nodes.
+When you instantiate a CellTree, you must pass in an instance of a concrete class that implements interface <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html">TreeViewModel</a>.  This concrete class gets and organizes the data into a hierarchy in the implementation of method getNodeInfo(value).  When a tree node is opened, the tree calls <a href="/javadoc/latest/com/google/gwt/view/client/TreeViewModel.html#getNodeInfo(T)">getNodeInfo(value)</a> to get the data provider and Cell used to render the child nodes.
 </p>
 
 <p>
@@ -367,7 +367,7 @@
 </p>
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellBrowser">CwCellBrowser example</a> shows a CellBrowser.  It displays the same data in the same three levels as the above CellTree example, except that it displays the levels side-by-side.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellBrowser">CwCellBrowser example</a> shows a CellBrowser.  It displays the same data in the same three levels as the above CellTree example, except that it displays the levels side-by-side.
 </p>
 
 <p>
@@ -381,11 +381,11 @@
 </p>
 
 <p>
-<b>Code Example #1</b> - For a simple example of CellBrowser, see <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellBrowserExample.java">CellBrowerExample.java</a>. 
+<b>Code Example #1</b> - For a simple example of CellBrowser, see <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellBrowserExample.java">CellBrowerExample.java</a>. 
 </p>
 
 <p>
-<b>Code Example #2</b> - For a real-world example of CellBrowser, see <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellBrowserExample2.java">CellBrowserExample2.java</a>.
+<b>Code Example #2</b> - For a real-world example of CellBrowser, see <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellBrowserExample2.java">CellBrowserExample2.java</a>.
 </p>
 
 <h2 class="h2-group" id="Cells">Cells</h2>
@@ -393,7 +393,7 @@
 <h2 id="available">Available Cell Types</h2>
 
 <p>
-GWT offers a number of concrete Cell implementations that you can use immediately. See the <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellSampler">Cell Sampler </a>for examples.
+GWT offers a number of concrete Cell implementations that you can use immediately. See the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellSampler">Cell Sampler </a>for examples.
 </p>
 
 <dl>
@@ -499,7 +499,7 @@
 
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a CellList&lt;ContactInfo&gt; (on the left). Each list item is a custom type ContactCell&lt;ContactInfo&gt;.  The right-hand widget is a normal Composite widget that renders the data for a selected contact.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a CellList&lt;ContactInfo&gt; (on the left). Each list item is a custom type ContactCell&lt;ContactInfo&gt;.  The right-hand widget is a normal Composite widget that renders the data for a selected contact.
 </p>
 
 
@@ -514,7 +514,7 @@
 
 
 <p>
-For demonstrations of selection, the <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CwCellList</a> widget creates a SingleSelectionModel, whereas CwCellTable implements a MultiSelectionModel using checkboxes.
+For demonstrations of selection, the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CwCellList</a> widget creates a SingleSelectionModel, whereas CwCellTable implements a MultiSelectionModel using checkboxes.
 </p>
 
 
@@ -538,7 +538,7 @@
 
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a cell widget that has a SelectionModel added to it. Clicking on an item selects it.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CwCellList example</a> shows a cell widget that has a SelectionModel added to it. Clicking on an item selects it.
 </p>
 
 
@@ -556,7 +556,7 @@
 </ol>
 
 <p>
-<b>Code Example</b> - The example of SelectionModel below is available at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellListExample.java">CellListExample.java</a>.
+<b>Code Example</b> - The example of SelectionModel below is available at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellListExample.java">CellListExample.java</a>.
 </p>
 
 <pre class="prettyprint">
@@ -621,7 +621,7 @@
 Keys allow us to associate ViewData, such as selection state and validation information, with a DTO.  If you select some items in a table or list, then when the list refreshes with new data, you can maintain the same selection.
 </p>
 
-<p><b>Code Example</b> - The example of KeyProvider below is available at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/view/KeyProviderExample.java">KeyProviderExample.java</a>.</p>
+<p><b>Code Example</b> - The example of KeyProvider below is available at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/view/KeyProviderExample.java">KeyProviderExample.java</a>.</p>
 
 <pre class="prettyprint">
 /**
@@ -935,11 +935,11 @@
 </p>
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> shows a SimplePager control below a table.
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> shows a SimplePager control below a table.
 </p>
 
 <p>
-<b>Code Example</b> - The example below is available at  <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/SimplePagerExample.java">SimplePagerExample.java</a>.
+<b>Code Example</b> - The example below is available at  <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/SimplePagerExample.java">SimplePagerExample.java</a>.
 </p>
 
 <p>
@@ -1038,7 +1038,7 @@
 <b>Demo</b> - <i>(none)</i>
 </p>
 <p>
-<b>Code Example</b> - The example below is available at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellListValueUpdaterExample.java">CellListValueUpdaterExample.java</a>.
+<b>Code Example</b> - The example below is available at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellListValueUpdaterExample.java">CellListValueUpdaterExample.java</a>.
 </p>
 
 <p>
@@ -1103,7 +1103,7 @@
 </p>
 
 <p>
-<b>Demo</b> - <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> lets you modify the First and Last names (these columns use <a href="#text-cells">EditTextCell</a>).
+<b>Demo</b> - <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTable">CwCellTable example</a> lets you modify the First and Last names (these columns use <a href="#text-cells">EditTextCell</a>).
 </p>
 
 <p>
@@ -1116,7 +1116,7 @@
 </ol>
 
 <p>
-<b>Code Example</b> - An example is available at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cellview/CellTableFieldUpdaterExample.java">CellTableFieldUpdaterExample.java</a>.
+<b>Code Example</b> - An example is available at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cellview/CellTableFieldUpdaterExample.java">CellTableFieldUpdaterExample.java</a>.
 </p>
 
 <pre class="prettyprint">
diff --git a/src/main/markdown/doc/latest/DevGuideUiCss.md b/src/main/markdown/doc/latest/DevGuideUiCss.md
index a88c85d..3a8b71a 100644
--- a/src/main/markdown/doc/latest/DevGuideUiCss.md
+++ b/src/main/markdown/doc/latest/DevGuideUiCss.md
@@ -65,7 +65,7 @@
 <p>In the above style sheet code, there are two style rules that apply to menu items. The first applies to all menu items (both selected and unselected), while the second (with
 the -selected suffix) applies only to selected menu items. A selected menu item's style name will be set to <tt>&quot;gwt-MenuItem gwt-MenuItem-selected&quot;</tt>, specifying that both
 style rules will be applied. The most common way of doing this is to use <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setStyleName(java.lang.String)">setStyleName</a> to set
-the base style name, then <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#addStyleName(java.lang.String)">addStyleName()</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#removeStyleName(java.lang.String)">removeStyleName()</a>
+the base style name, then <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#addStyleName(java.lang.String)">addStyleName()</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#removeStyleName(java.lang.String)">removeStyleName()</a>
 to add and remove the second style name.</p>
 
 <h2 id="cssfiles">Associating CSS Files</h2>
@@ -151,4 +151,4 @@
 
 <h2 id="documentation">Documentation</h2>
 
-<p>It is standard practice to document the relevant CSS style names for each widget class as part of its documentation comment. For a simple example, see <a href="/javadoc/latest/com/google/gwt/user/client/ui/Button.html">Button</a>. For a more complex example, see <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a>.</p>
\ No newline at end of file
+<p>It is standard practice to document the relevant CSS style names for each widget class as part of its documentation comment. For a simple example, see <a href="/javadoc/latest/com/google/gwt/user/client/ui/Button.html">Button</a>. For a more complex example, see <a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a>.</p>
\ No newline at end of file
diff --git a/src/main/markdown/doc/latest/DevGuideUiCustomCells.md b/src/main/markdown/doc/latest/DevGuideUiCustomCells.md
index f108cc1..1c12748 100644
--- a/src/main/markdown/doc/latest/DevGuideUiCustomCells.md
+++ b/src/main/markdown/doc/latest/DevGuideUiCustomCells.md
@@ -40,7 +40,7 @@
 Cell#render(Context, C value, SafeHtmlBuilder)</a>
 method, which renders the parameterized <code>value</code> into the <code>SafeHtmlBuilder</code>.  In some cases, you will only need to render
 simple HTML, such as a single <code>div</code> with some content.  In other cases, you might need to render a complex HTML structure, such as the one
-in the <a href="http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList">CellList</a> example, which contains an image and two lines of
+in the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList">CellList</a> example, which contains an image and two lines of
 text. The basic principles are the same in either case.
 </p>
 
@@ -90,7 +90,7 @@
 </p>
 
 <p>
-You can download this example at <a href="http://google-web-toolkit.googlecode.com/svn/trunk/user/javadoc/com/google/gwt/examples/cell/CellExample.java">CellExample.java</a>.
+You can download this example at <a href="https://gwt.googlesource.com/gwt/+/master/user/javadoc/com/google/gwt/examples/cell/CellExample.java">CellExample.java</a>.
 </p>
 
 <pre class="prettyprint">
diff --git a/src/main/markdown/doc/latest/DevGuideUiCustomWidgets.md b/src/main/markdown/doc/latest/DevGuideUiCustomWidgets.md
index 1b545a5..fae864b 100644
--- a/src/main/markdown/doc/latest/DevGuideUiCustomWidgets.md
+++ b/src/main/markdown/doc/latest/DevGuideUiCustomWidgets.md
@@ -26,7 +26,7 @@
 <h3>Example Composite Widget</h3>
 
 <p>The following code snippet shows how to create a composite widget composed of a <a href="/javadoc/latest/com/google/gwt/user/client/ui/TextBox.html" >TextBox</a> widget and a
-<a href="/javadoc/latest/com/google/gwt/user/client/ui/CheckBox.html">CheckBox</a> widget laid out in a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/VerticalPanel.html">VerticalPanel</a>.</p>
+<a href="/javadoc/latest/com/google/gwt/user/client/ui/CheckBox.html">CheckBox</a> widget laid out in a <a href="/javadoc/latest/com/google/gwt/user/client/ui/VerticalPanel.html">VerticalPanel</a>.</p>
 
 <pre class="prettyprint">
 package com.google.gwt.examples;
@@ -114,7 +114,7 @@
 <h2 id="new">From Scratch in Java Code</h2>
 
 <p>It is also possible to create a widget from scratch, although it is trickier since you have to write code at a lower level. Many of the basic widgets are written this way, such
-as <a href="/javadoc/latest/com/google/gwt/user/client/ui/Button.html">Button</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/TextBox.html">TextBox</a>. Please refer to the implementations of these
+as <a href="/javadoc/latest/com/google/gwt/user/client/ui/Button.html">Button</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/TextBox.html">TextBox</a>. Please refer to the implementations of these
 widgets to understand how to create your own.</p>
 
 <p>To understand how to create your own, refer to the implementations of these widgets in the com.google.gwt.user.client.ui package. The source code is in gwt-user.jar.</p>
diff --git a/src/main/markdown/doc/latest/DevGuideUiDom.md b/src/main/markdown/doc/latest/DevGuideUiDom.md
index 6688c7d..cfd8a32 100644
--- a/src/main/markdown/doc/latest/DevGuideUiDom.md
+++ b/src/main/markdown/doc/latest/DevGuideUiDom.md
@@ -43,7 +43,7 @@
 structure and adds a style attribute to it.</p>
 
 <p>This is an example where using the DOM isn't absolutely necessary. An alternative approach is to use <a href="DevGuideUiCss.html">style sheets</a> and
-associate different style classes to the widget using the <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setStylePrimaryName(java.lang.String)">setStylePrimaryName()</a> or <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setStyleName(java.lang.String)">setStyleName()</a> method
+associate different style classes to the widget using the <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setStylePrimaryName(java.lang.String)">setStylePrimaryName()</a> or <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setStyleName(java.lang.String)">setStyleName()</a> method
 instead.</p>
 
 <h2>Finding an element in the DOM</h2>
diff --git a/src/main/markdown/doc/latest/DevGuideUiEditors.md b/src/main/markdown/doc/latest/DevGuideUiEditors.md
index 8a6e429..24fd0fa 100644
--- a/src/main/markdown/doc/latest/DevGuideUiEditors.md
+++ b/src/main/markdown/doc/latest/DevGuideUiEditors.md
@@ -264,7 +264,7 @@
   <ul>
     <li>The <code>ListEditor</code> is created with a user-provided <code>EditorSource</code> which vends sub-Editors (usually Widget subtypes).</li>
     <li>Changes made to the structure of the <code>List</code> returned by <code>ListEditor.getList()</code> will be reflected in calls made to the <code>EditorSource</code>.</li>
-    <li><a href="http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/dynatablerf/#dynatablerf/src/main/java/com/google/gwt/sample/dynatablerf/client/widgets/FavoritesWidget.java" rel="nofollow">Sample code</a>.</li>
+    <li><a href="https://gwt.googlesource.com/gwt/+/master/samples/dynatablerf/#dynatablerf/src/main/java/com/google/gwt/sample/dynatablerf/client/widgets/FavoritesWidget.java" rel="nofollow">Sample code</a>.</li>
   </ul>
 
   <li><code>OptionalFieldEditor</code> can be used with nullable or resettable bean properties.</li>
diff --git a/src/main/markdown/doc/latest/DevGuideUiPanels.md b/src/main/markdown/doc/latest/DevGuideUiPanels.md
index d595467..2d831ef 100644
--- a/src/main/markdown/doc/latest/DevGuideUiPanels.md
+++ b/src/main/markdown/doc/latest/DevGuideUiPanels.md
@@ -49,12 +49,12 @@
 a <a href="/javadoc/latest/com/google/gwt/user/client/ui/ScrollPanel.html">ScrollPanel</a>. This panel works well in layout panels (see below), which
 provide it with the explicit size it needs to scroll properly.</p>
 
-<h3><a href="/javadoc/latest/com/google/gwt/user/client/ui/PopupPanel.html">PopupPanel</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/DialogBox.html">DialogBox</a></h3>
+<h3><a href="/javadoc/latest/com/google/gwt/user/client/ui/PopupPanel.html">PopupPanel</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/DialogBox.html">DialogBox</a></h3>
 
 <p>Use these two panels to create simple popups and modal dialogs. They overlap
 existing content in browser window, and can be stacked over one-another.</p>
 
-<h3><a href="/javadoc/latest/com/google/gwt/user/client/ui/Grid.html">Grid</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/FlexTable.html">FlexTable</a></h3>
+<h3><a href="/javadoc/latest/com/google/gwt/user/client/ui/Grid.html">Grid</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/FlexTable.html">FlexTable</a></h3>
 
 <p>These two widgets are used to create traditional HTML <code>&lt;table&gt;</code> elements, and can
 also be used as panels, in that arbitrary widgets may be added to their cells.</p>
@@ -107,7 +107,7 @@
 
 <h3><a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a></h3>
 
-<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> serves the same purpose as the existing <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/DockPanel.html">DockPanel</a> widget,
+<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> serves the same purpose as the existing <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockPanel.html">DockPanel</a> widget,
 except that it uses the layout system to achieve this structure without using
 tables, and in a predictable manner. You would often use to build
 application-level structure, as in the following example:</p>
@@ -128,10 +128,10 @@
 
 <h3>SplitLayoutPanel</h3>
 
-<p>The <a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> is identical to the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> (and indeed
+<p>The <a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> is identical to the <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> (and indeed
 extends it), except that it automatically creates a user-draggable splitter
 between each pair of child widgets. It also supports only the use of pixel
-units. Use this instead of <a href="/javadoc/latest/com/google/gwt/user/client/ui/HorizontalSplitPanel.html">HorizontalSplitPanel</a> and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/VerticalSplitPanel.html">VerticalSplitPanel</a>.</p>
+units. Use this instead of <a href="/javadoc/latest/com/google/gwt/user/client/ui/HorizontalSplitPanel.html">HorizontalSplitPanel</a> and <a href="/javadoc/latest/com/google/gwt/user/client/ui/VerticalSplitPanel.html">VerticalSplitPanel</a>.</p>
 
 <pre class='prettyprint'>SplitLayoutPanel p = new SplitLayoutPanel();
 p.addWest(new HTML("navigation"), 128);
@@ -143,7 +143,7 @@
 
 <h3>StackLayoutPanel</h3>
 
-<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/StackLayoutPanel.html">StackLayoutPanel</a> replaces the existing <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/StackPanel.html">StackPanel</a> (which does not work very
+<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/StackLayoutPanel.html">StackLayoutPanel</a> replaces the existing <a href="/javadoc/latest/com/google/gwt/user/client/ui/StackPanel.html">StackPanel</a> (which does not work very
 well in standards mode). It displays one child widget at a time, each of which is
 associated with a single "header" widget. Clicking on a header widget shows its
 associated child widget.</p>
@@ -162,7 +162,7 @@
 
 <h3>TabLayoutPanel</h3>
 
-<p>As with the existing <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabPanel.html">TabPanel</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/TabLayoutPanel.html">TabLayoutPanel</a> displays a row of clickable
+<p>As with the existing <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabPanel.html">TabPanel</a>, <a href="/javadoc/latest/com/google/gwt/user/client/ui/TabLayoutPanel.html">TabLayoutPanel</a> displays a row of clickable
 tabs. Each tab is associated with another child widget, which is shown when a
 user clicks on the tab.</p>
 
@@ -191,8 +191,8 @@
 necessary to support a number of use-cases, because the layout system must
 properly handle animation among sets of layout constraints.</p>
 
-<p>Panels that implement <a href="/javadoc/latest/com/google/gwt/user/client/ui/AnimatedLayout.html">AnimatedLayout</a>, such as <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/LayoutPanel.html">LayoutPanel</a>,
-<a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a>, and <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a>, can animate their child widgets from
+<p>Panels that implement <a href="/javadoc/latest/com/google/gwt/user/client/ui/AnimatedLayout.html">AnimatedLayout</a>, such as <a href="/javadoc/latest/com/google/gwt/user/client/ui/LayoutPanel.html">LayoutPanel</a>,
+<a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a>, and <a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a>, can animate their child widgets from
 one set of constraints to another. Typically this is done by setting up the
 state towards which you wish to animate, then calling
 <a href="/javadoc/latest/com/google/gwt/user/client/ui/AnimatedLayout.html#animate(int)">animate()</a>. See <a href="#recipes">"Recipes"</a>
@@ -234,7 +234,7 @@
 <h3>ResizeComposite</h3>
 
 <p>When creating a custom <a href="/javadoc/latest/com/google/gwt/user/client/ui/Composite.html">Composite</a> widget that wrap a widget that implements
-<a href="/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html">RequiresResize</a>, you should use <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/ResizeComposite.html">ResizeComposite</a> as its base class. This
+<a href="/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html">RequiresResize</a>, you should use <a href="/javadoc/latest/com/google/gwt/user/client/ui/ResizeComposite.html">ResizeComposite</a> as its base class. This
 subclass of <a href="/javadoc/latest/com/google/gwt/user/client/ui/Composite.html">Composite</a> automatically propagates resize events to its wrapped
 widget.</p>
 
@@ -261,7 +261,7 @@
 allocates space to individual table rows and columns that can lead to
 unexpected behavior in standards mode.</p>
 
-<p>You should use <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> in place of <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/DockPanel.html">DockPanel</a>. <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/VerticalPanel.html">VerticalPanel</a> can
+<p>You should use <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a> in place of <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockPanel.html">DockPanel</a>. <a href="/javadoc/latest/com/google/gwt/user/client/ui/VerticalPanel.html">VerticalPanel</a> can
 usually be replaced by a simple <a href="/javadoc/latest/com/google/gwt/user/client/ui/FlowPanel.html">FlowPanel</a> (since block-level elements will
 naturally stack up vertically).</p>
 
@@ -399,7 +399,7 @@
 
 <h3>Splitters</h3>
 
-<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> works much like <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a>, except that it only
+<p><a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> works much like <a href="/javadoc/latest/com/google/gwt/user/client/ui/DockLayoutPanel.html">DockLayoutPanel</a>, except that it only
 supports pixel units. The basic application structure above can be given a
 splitter between the navigation and content areas like so:</p>
 
@@ -450,9 +450,9 @@
 
 <h3>Implementing a Composite that RequiresResize</h3>
 
-<p>Widgets that implement <a href="/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html">RequiresResize</a> expect <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html#onResize()">RequiresResize.onResize()</a> to
+<p>Widgets that implement <a href="/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html">RequiresResize</a> expect <a href="/javadoc/latest/com/google/gwt/user/client/ui/RequiresResize.html#onResize()">RequiresResize.onResize()</a> to
 be called whenever the widget's size changes. If you are wrapping such a widget
-in a <a href="/javadoc/latest/com/google/gwt/user/client/ui/Composite.html">Composite</a>, you'll need to use <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/ResizeComposite.html">ResizeComposite</a> instead to ensure that
+in a <a href="/javadoc/latest/com/google/gwt/user/client/ui/Composite.html">Composite</a>, you'll need to use <a href="/javadoc/latest/com/google/gwt/user/client/ui/ResizeComposite.html">ResizeComposite</a> instead to ensure that
 this call is propagated correctly, like so:</p>
 
 <pre class='prettyprint'>class MyWidget extends ResizeComposite {
@@ -468,7 +468,7 @@
 
 <p>The <a href="/javadoc/latest/com/google/gwt/layout/client/Layout.html">Layout</a> class has to wrap each of its child elements in a "container"
 element in order to work properly. One implication of this is that, when you
-call <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setVisible(boolean)">UIObject.setVisible(boolean)</a> on a widget within a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/LayoutPanel.html">LayoutPanel</a>, it
+call <a href="/javadoc/latest/com/google/gwt/user/client/ui/UIObject.html#setVisible(boolean)">UIObject.setVisible(boolean)</a> on a widget within a <a href="/javadoc/latest/com/google/gwt/user/client/ui/LayoutPanel.html">LayoutPanel</a>, it
 won't behave quite as expected: the widget will indeed be made invisible, but
 it will tend to consume mouse events (actually, it's the container element that
 is doing so).</p>
@@ -490,7 +490,7 @@
 <a href="/javadoc/latest/com/google/gwt/user/client/ui/ProvidesResize.html">ProvidesResize</a>.</p>
 
 <p>There are, however, instances where you need to use a layout panel within a
-normal widget (e.g., <a href="/javadoc/latest/com/google/gwt/user/client/ui/FlowPanel.html">FlowPanel</a> or <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/RootPanel.html">RootPanel</a>). In these cases, you will need
+normal widget (e.g., <a href="/javadoc/latest/com/google/gwt/user/client/ui/FlowPanel.html">FlowPanel</a> or <a href="/javadoc/latest/com/google/gwt/user/client/ui/RootPanel.html">RootPanel</a>). In these cases, you will need
 to set the panel's size explicitly, as in the following example:</p>
 
 <pre class='prettyprint'>LayoutPanel panel = new LayoutPanel();
@@ -504,7 +504,7 @@
 you must do so manually.</p>
 
 <p>This also applies to layout panels used in <a href="/javadoc/latest/com/google/gwt/user/client/ui/PopupPanel.html">PopupPanel</a> and
-<a href="/javadoc/latest/com/google/gwt/user/client/ui/DialogBox.html">DialogBox</a>. The following example shows the use of a <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> in a
+<a href="/javadoc/latest/com/google/gwt/user/client/ui/DialogBox.html">DialogBox</a>. The following example shows the use of a <a href="/javadoc/latest/com/google/gwt/user/client/ui/SplitLayoutPanel.html">SplitLayoutPanel</a> in a
 <a href="/javadoc/latest/com/google/gwt/user/client/ui/DialogBox.html">DialogBox</a>:</p>
 
 <pre class='prettyprint'>SplitLayoutPanel split = new SplitLayoutPanel();
diff --git a/src/main/markdown/doc/latest/FAQ_UI.md b/src/main/markdown/doc/latest/FAQ_UI.md
index 1e8a416..cc8fbba 100644
--- a/src/main/markdown/doc/latest/FAQ_UI.md
+++ b/src/main/markdown/doc/latest/FAQ_UI.md
@@ -130,7 +130,7 @@
 the browser resizes.
 </p>
 
-<p>The <a href="http://gwt.google.com/samples/Mail/Mail.html">Mail sample application</a> demonstrates SplitLayoutPanel in action.</p>
+<p>The <a href="http://samples.gwtproject.org/samples/Mail/Mail.html">Mail sample application</a> demonstrates SplitLayoutPanel in action.</p>
 
 <p>See the Developer's Guide on <a href="DevGuideUiPanels.html#LayoutPanels">Layout Panels</a> for more details and code snippets.
 
diff --git a/src/main/markdown/doc/latest/RefWidgetGallery.md b/src/main/markdown/doc/latest/RefWidgetGallery.md
index d119a72..60d50e4 100644
--- a/src/main/markdown/doc/latest/RefWidgetGallery.md
+++ b/src/main/markdown/doc/latest/RefWidgetGallery.md
@@ -4,7 +4,7 @@
 
 <p>The following are <a href="#Widgets">widgets</a> and <a
   href="#Panels">panels</a> available in the GWT user-interface library. You
-can view a code example of each widget in the <a href="http://gwt.google.com/samples/Showcase/Showcase.html">Showcase</a> sample application.</p>
+can view a code example of each widget in the <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html">Showcase</a> sample application.</p>
 
 <p>
 <b>Widgets:</b><br>
@@ -101,7 +101,7 @@
   <dt id="menubar"><a href="/javadoc/latest/com/google/gwt/user/client/ui/MenuBar.html">MenuBar</a></dt>
   <dd><img src="images/MenuBar.png"/></dd>
   
-  <dt id="tree"><a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a>, <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/cellview/client/CellTree.html">CellTree</a></dt>
+  <dt id="tree"><a href="/javadoc/latest/com/google/gwt/user/client/ui/Tree.html">Tree</a>, <a href="/javadoc/latest/com/google/gwt/user/cellview/client/CellTree.html">CellTree</a></dt>
   <dd><img src="images/Tree.png"/></dd>
   
   <dt id="suggestbox"><a href="/javadoc/latest/com/google/gwt/user/client/ui/SuggestBox.html">SuggestBox</a></dt>
diff --git a/src/main/markdown/doc/latest/tutorial/buildui.md b/src/main/markdown/doc/latest/tutorial/buildui.md
index de01699..9d1ea71 100644
--- a/src/main/markdown/doc/latest/tutorial/buildui.md
+++ b/src/main/markdown/doc/latest/tutorial/buildui.md
@@ -167,7 +167,7 @@
     <li>Save the file StockWatcher.html.</li>
 </ol>
 <pre class="code">
-&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"&gt;
+&lt;!DOCTYPE html&gt;
 &lt;html&gt;
   &lt;head&gt;
     &lt;meta http-equiv="content-type" content="text/html; charset=UTF-8"&gt;
diff --git a/src/main/markdown/doc/latest/tutorial/manageevents.md b/src/main/markdown/doc/latest/tutorial/manageevents.md
index bcbd6a7..4261166 100644
--- a/src/main/markdown/doc/latest/tutorial/manageevents.md
+++ b/src/main/markdown/doc/latest/tutorial/manageevents.md
@@ -44,7 +44,7 @@
     </tr>
 </table>
 <p>
-GWT provides a number of different event handler interfaces. To handle click events on the Add and Remove buttons, you'll use the <a href="/javadoc/latest/com/google/gwt/event/dom/client/ClickHandler.html">ClickHandler</a> interface. To handle keyboard events in the input box, you'll use the <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/event/dom/client/KeyPressHandler.html">KeyPressHandler</a> interface.
+GWT provides a number of different event handler interfaces. To handle click events on the Add and Remove buttons, you'll use the <a href="/javadoc/latest/com/google/gwt/event/dom/client/ClickHandler.html">ClickHandler</a> interface. To handle keyboard events in the input box, you'll use the <a href="/javadoc/latest/com/google/gwt/event/dom/client/KeyPressHandler.html">KeyPressHandler</a> interface.
 </p>
 
 <p class="note">
diff --git a/src/main/markdown/examples.md b/src/main/markdown/examples.md
index 8d39a83..e8a1da3 100644
--- a/src/main/markdown/examples.md
+++ b/src/main/markdown/examples.md
@@ -86,10 +86,10 @@
 
   <div class="project">
       <div class="screenshot">
-        <a href="http://gwt.google.com/samples/Showcase/Showcase.html" target="_blank"><img src="images/showcase.jpg" alt="Screenshot"/></a>
+        <a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html" target="_blank"><img src="images/showcase.jpg" alt="Screenshot"/></a>
       </div>
       <div class="info">
-        <div class="name"><a href="http://gwt.google.com/samples/Showcase/Showcase.html" target="_blank">GWT Showcase</a></div>
+        <div class="name"><a href="http://samples.gwtproject.org/samples/Showcase/Showcase.html" target="_blank">GWT Showcase</a></div>
         <div class="snippet">A showcase of GWT features with accompanying source code and CSS styles.</div>
         <div class="apis">
           <div class="head">GWT features used:</div>
@@ -101,10 +101,10 @@
 
     <div class="project">
       <div class="screenshot">
-        <a href="http://gwt.google.com/samples/Mail/Mail.html" target="_blank"><img src="images/mail.jpg" alt="Screenshot"/></a>
+        <a href="http://samples.gwtproject.org/samples/Mail/Mail.html" target="_blank"><img src="images/mail.jpg" alt="Screenshot"/></a>
       </div>
       <div class="info">
-        <div class="name"><a href="http://gwt.google.com/samples/Mail/Mail.html" target="_blank">Mail Application</a></div>
+        <div class="name"><a href="http://samples.gwtproject.org/samples/Mail/Mail.html" target="_blank">Mail Application</a></div>
         <div class="snippet">A replica of the UI of a desktop email application.</div>
         <div class="apis">
           <div class="head">GWT features used:</div>
@@ -116,21 +116,6 @@
 
     <div class="project">
       <div class="screenshot">
-        <a href="http://gwt.google.com/samples/DynaTable/DynaTable.html" target="_blank"><img src="images/dynamictable.jpg" alt="Screenshot"/></a>
-      </div>
-      <div class="info">
-        <div class="name"><a href="http://gwt.google.com/samples/DynaTable/DynaTable.html" target="_blank">Dynamic Table</a></div>
-        <div class="snippet">A table of data that demonstrates paging over objects retrieved through RPCs.</div>
-        <div class="apis">
-          <div class="head">GWT features used:</div>
-          <div class="item"><a href="doc/latest/DevGuideUiWidgets.html">UI widgets</a></div>
-          <div class="item"><a href="doc/latest/DevGuideServerCommunication.html#DevGuideRemoteProcedureCalls">Polymorphic RPC</a></div>
-        </div>
-      </div>
-    </div>
-
-    <div class="project">
-      <div class="screenshot">
         <a href="http://sticky.appspot.com" target="_blank"><img src="images/sticky.png" alt="Screenshot"/></a>
       </div>
       <div class="info">
diff --git a/src/main/markdown/overview.md b/src/main/markdown/overview.md
index a8c1d6c..dedda43 100644
--- a/src/main/markdown/overview.md
+++ b/src/main/markdown/overview.md
@@ -52,7 +52,7 @@
   </div>
   <br/>
   <div>
-    <a href="doc/latest/ReleaseNotes.html">What's New in GWT 2.5.1</a>
+    <a href="doc/latest/ReleaseNotes.html">What's New in GWT 2.6.1</a>
   </div>
 </div>
 
diff --git a/src/main/markdown/release-notes.md b/src/main/markdown/release-notes.md
index 321f5a9..ce5c4c7 100644
--- a/src/main/markdown/release-notes.md
+++ b/src/main/markdown/release-notes.md
@@ -1474,7 +1474,7 @@
 			<li>Select "Add/Remove Programs"</li>
 			<li>Select "GWT Developer Plugin for IE" then click "Uninstall"</li>
 			<li>Run Internet Explorer and browse to <a
-				href="http://gwt.google.com/samples/MissingPlugin">http://gwt.google.com/samples/MissingPlugin</a>
+				href="/missing-plugin/">http://gwtproject.org/missing-plugin/</a>
 				to install the new version of the plugin
 			</li>
 		</ol>