Issue #1349610 by bartlantz: Added make the subtopics of Field API link back to it.

core/modules/field/field.api.php

@@ -115,6 +115,8 @@ function hook_field_extra_fields_alter(&$info) {
  *
  * A third kind of pluggable handlers, storage backends, is defined by the
  * @link field_storage Field Storage API @endlink.
+ *
+ * @see field
  */
 
 /**

core/modules/field/field.attach.inc

@@ -44,6 +44,8 @@ function __construct($errors) {
  *
  * Each field defines which storage backend it uses. The Drupal system variable
  * 'field_storage_default' identifies the storage backend used by default.
+ *
+ * @see field
  */
 
 /**
@@ -117,6 +119,8 @@ function __construct($errors) {
  * The pre-operation hooks do not make the Field Storage API irrelevant. The
  * Field Storage API is essentially the "fallback mechanism" for any fields
  * that aren't being intercepted explicitly by pre-operation hooks.
+ *
+ * @see field
  */
 
 /**

core/modules/field/field.crud.inc

@@ -15,6 +15,8 @@
  *
  * The Field CRUD API uses
  * @link field Field API data structures @endlink.
+ *
+ * @see field
  */
 
 /**
@@ -824,6 +826,8 @@ function field_delete_instance($instance, $field_cleanup = TRUE) {
  *     ),
  *   );
  * @endcode
+ *
+ * @see field
  */
 
 /**

core/modules/field/field.info.inc

@@ -13,6 +13,8 @@
  * The Field Info API exposes information about field types, fields,
  * instances, bundles, widget types, display formatters, behaviors,
  * and settings defined by or with the Field API.
+ *
+ * @see field
  */
 
 /**

core/modules/field/field.multilingual.inc

@@ -57,6 +57,8 @@
  *   even disabled by modules implementing hook_field_language_alter(), making
  *   it possible to choose the first approach. The display language for each
  *   field is returned by field_language().
+ *
+ * @see field
  */
 
 /**