diff --git a/core/includes/ajax.inc b/core/includes/ajax.inc
index 8817356..9a4360f 100644
--- a/core/includes/ajax.inc
+++ b/core/includes/ajax.inc
@@ -167,8 +167,8 @@
  * - #ajax['progress']: Choose either a throbber or progress bar that is
  *   displayed while awaiting a response from the callback, and add an optional
  *   message. Possible keys: 'type', 'message', 'url', 'interval'.
- *   More information is available in the
- *   @link http://api.drupal.org/api/drupal/developer--topics--forms_api_reference.html/7 Form API Reference @endlink
+ *   More information is available in the Form API reference
+ *   (forms_api_reference.html)
  *
  * In addition to using Form API for doing in-form modification, Ajax may be
  * enabled by adding classes to buttons and links. By adding the 'use-ajax'
diff --git a/core/includes/form.inc b/core/includes/form.inc
index 6ebbac4..7fa0e87 100644
--- a/core/includes/form.inc
+++ b/core/includes/form.inc
@@ -78,9 +78,7 @@
  * The $form argument to form-related functions is a structured array containing
  * the elements and properties of the form. For information on the array
  * components and format, and more detailed explanations of the Form API
- * workflow, see the
- * @link http://api.drupal.org/api/drupal/developer--topics--forms_api_reference.html Form API reference @endlink
- * and the
+ * workflow, see the Form API reference (forms_api_reference.html) and the
  * @link http://drupal.org/node/37775 Form API documentation section. @endlink
  * In addition, there is a set of Form API tutorials in
  * @link form_example_tutorial.inc the Form Example Tutorial @endlink which
@@ -214,10 +212,9 @@ function drupal_get_form($form_id) {
  *     set.
  *   - values: An associative array of values submitted to the form. The
  *     validation functions and submit functions use this array for nearly all
- *     their decision making. (Note that
- *     @link http://api.drupal.org/api/drupal/developer--topics--forms_api_reference.html/7#tree #tree @endlink
- *     determines whether the values are a flat array or an array whose
- *     structure parallels the $form array.)
+ *     their decision making. (Note that the Form API reference
+ *     (forms_api_reference.html) determines whether the values are a flat
+ *     array or an array whose structure parallels the $form array.)
  *   - input: The array of values as they were submitted by the user. These are
  *     raw and unvalidated, so should not be used without a thorough
  *     understanding of security implications. In almost all cases, code should
diff --git a/core/modules/field/field.api.php b/core/modules/field/field.api.php
index 774d8b5..8e71b1d 100644
--- a/core/modules/field/field.api.php
+++ b/core/modules/field/field.api.php
@@ -667,11 +667,10 @@ function hook_field_is_empty($item, $field) {
  * which widget to use. Widget types are defined by implementing
  * hook_field_widget_info().
  *
- * Widgets are
- * @link http://api.drupal.org/api/drupal/developer--topics--forms_api_reference.html Form API @endlink
- * elements with additional processing capabilities. Widget hooks are typically
- * called by the Field Attach API during the creation of the field form
- * structure with field_attach_form().
+ * Widgets are, see the Form API reference (forms_api_reference.html) elements
+ * with additional processing capabilities. Widget hooks are typically called
+ * by the Field Attach API during the creation of the field form structure with
+ * field_attach_form().
  *
  * @see field
  * @see field_types