Merge pull request #1085 from dsenalik/tripaltypos20200912

343 more corrections for typos

docs/dev_guide/custom_field/create_instance.rst

@@ -42,11 +42,11 @@ When the site administrator navigates to **Administer > Structure > Tripal Conte
 
 Programmatically Attaching Fields
 ---------------------------------
-You probably want to programmatically attach fields to content types if your have existing data that you know should be made available. For example, an organism always has a genus and only one genus.  If we have a field that displays the genus for an organism then we will want it automatically attached on installation of our module.  We can do this programmatically using two hook functions: ``hook_bundle_fields_info()`` and ``hook_bundle_instance_info()``.  Both functions are required to attach a field to a content type. 
+You probably want to programmatically attach fields to content types if your have existing data that you know should be made available. For example, an organism always has a genus and only one genus.  If we have a field that displays the genus for an organism then we will want it automatically attached on installation of our module.  We can do this programmatically using two hook functions: ``hook_bundle_fields_info()`` and ``hook_bundle_instances_info()``.  Both functions are required to attach a field to a content type. 
 
-The hook_bundle_instance_info() function.
+The hook_bundle_instances_info() function.
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The previous hook tells Drupal that our field exists and is allowed to be connected to the organism bundle.  Next we need to create an actual instance of this field for the bundle.  We do this with the ``hook_bundle_instance_info()`` function.  The format is the same as the previous hook but the info array is different.  For example:
+The previous hook tells Drupal that our field exists and is allowed to be connected to the organism bundle.  Next we need to create an actual instance of this field for the bundle.  We do this with the ``hook_bundle_instances_info()`` function.  The format is the same as the previous hook but the info array is different.  For example:
 
 .. code-block:: php
   :linenos:
@@ -130,9 +130,9 @@ The following setting will allow the field to be added:
 
  public static $no_ui = FALSE;
 
-Next, we must let Drupal know that our field exists.  We do this by adding an entry to the ``$info`` array of in the ``hook_bundle_fields_info()`` function described above.  This lets Drupal know about our field. However, because we are not programmatically creating an instance of the field on a content type, but allowing the user to create them we do not need to implement the ``hook_bundle_instance_info()`` function. Instead, we must implement ``hook_bundle_create_user_field()``.  This function is called when the user attempts to add our new field to a bundle.  One field that comes with Tripal is the ``chado_linker__prop`` field.  Most Chado base tables have an associated property table (e.g. ``organismprop``, ``featureprop``, ``stockprop``, etc). By default, the ``tripal_chado`` module automatically adds this field to all bundles that have existing properties. It adds a new instance for every property type.  However, new properties can be added to bundle, and the site admin may want to add those properties via the user interface rather. Therefore, this field has the ``$no_ui`` set to TRUE and uses the  ``hook_bundle_create_user_field()`` to create the new field instance for the user.
+Next, we must let Drupal know that our field exists.  We do this by adding an entry to the ``$info`` array in the ``hook_bundle_fields_info()`` function described above.  This lets Drupal know about our field. However, because we are not programmatically creating an instance of the field on a content type, but allowing the user to create them we do not need to implement the ``hook_bundle_instances_info()`` function. Instead, we must implement ``hook_bundle_create_user_field()``.  This function is called when the user attempts to add our new field to a bundle.  One field that comes with Tripal is the ``chado_linker__prop`` field.  Most Chado base tables have an associated property table (e.g. ``organismprop``, ``featureprop``, ``stockprop``, etc). By default, the ``tripal_chado`` module automatically adds this field to all bundles that have existing properties. It adds a new instance for every property type.  However, new properties can be added to bundle, and the site admin may want to add those properties via the user interface rather. Therefore, this field has the ``$no_ui`` set to TRUE and uses the  ``hook_bundle_create_user_field()`` to create the new field instance for the user.
 
-The following code is a snippet from the ``tripal_chado_bundle_create_user_field`` function of the ``tripal_chado`` module. Note that it uses the ``field_create_field`` function and the ``field_create_instance`` functions directly.  The arrays passed to these functions are identical to the ``$info`` arrays of both the ``hook_bundle_fields_info`` and ``hook_bundle_instance_info`` functions described above.
+The following code is a snippet from the ``tripal_chado_bundle_create_user_field`` function of the ``tripal_chado`` module. Note that it uses the ``field_create_field`` function and the ``field_create_instance`` functions directly.  The arrays passed to these functions are identical to the ``$info`` arrays of both the ``hook_bundle_fields_info`` and ``hook_bundle_instances_info`` functions described above.
 
 .. code-block:: php
   :linenos:
@@ -218,6 +218,6 @@ The following code is a snippet from the ``tripal_chado_bundle_create_user_field
 
 .. note::
   
-  It is possible to have a field that is both programmatically attached to some content types but is also allowed to be attached to another content type by the site admin using the web interface. To do this, programmatically add the field to the content types using the ``hook_bundle_instance_info`` function and also implement the ``hook_bundle_create_user_field`` function to support manual adding.
+  It is possible to have a field that is both programmatically attached to some content types but is also allowed to be attached to another content type by the site admin using the web interface. To do this, programmatically add the field to the content types using the ``hook_bundle_instances_info`` function and also implement the ``hook_bundle_create_user_field`` function to support manual adding.
   
  

docs/dev_guide/custom_field/custom_formatter.rst

@@ -162,7 +162,7 @@ The form shown in the screenshot above is provided by the ``settingsForm()`` fun
   
 The form is typical of any form.  Note, however that the ``#default_value`` is set using the current settings values.
 
-A settings form is useful but it only works when Drupal knows what settings you want for your field.  You must provide the settings names (e.g. "title" and "empty" in this case) when you  attach your field to a given content type (i.e. bundle).  You tell Drupal to attach this field to a content type using the ``hook_bundle_instance_info`` function.  See 
+A settings form is useful but it only works when Drupal knows what settings you want for your field.  You must provide the settings names (e.g. "title" and "empty" in this case) when you  attach your field to a given content type (i.e. bundle).  You tell Drupal to attach this field to a content type using the ``hook_bundle_instances_info`` function.  See 
 the :doc:`create_instance` to learn more about this function.  Briefly, the ``display`` section of the info array for the ``sbo__relationship`` field contains the following settings for the ``display``:
 
 .. code-block:: php

docs/dev_guide/custom_field/manual_field_creation.rst

@@ -60,9 +60,9 @@ As described in the section titled Tripal Data Structures, fields that are attac
 .. code-block:: php
 
   
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instance.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
@@ -121,12 +121,12 @@ Sometimes a field is meant to provide a visualization or some other functionalit
   public static $no_data = FALSE;
 
 
-  .. note::
+.. note::
   Be sure to only set this to TRUE when you are absolutely certain the contents would not be needed in web services.  Tripal was designed so that what appears on the page will always appear in web services.  Aside form the formatting we see on the website, the content should be the same.
 
 Finally, the last item in our Class variables is the **download_formatters**.  Tripal provides an API that allows tools to group entities into data collections.  Data collections are like "baskets" or "shopping carts".   Entities that are in data collections can be downloaded into files.  If your field is compatible with specific file downloaders you can specify those here.  A file downloader is a special TripalFieldDownloader class that "speaks" certain file formats.  Tripal, by default, provides the TripalTabDownloader (for tab-delimited files), the TripalCSVDownloader (for CSV files), a TripalNucFASTADownloader for creating nucleotide FASTA files and a TripalProteinFASTADownloader for protein FASTA files.   If your field is compatible with any of these formatters you can specify them in the following array:
 
-.. .. code-block::
+.. code-block::
 
   // Indicates the download formats for this field.  The list must be the
   // name of a child class of the TripalFieldDownloader.
@@ -494,7 +494,7 @@ As described above in the elementInfo function section, some fields and elements
       }
     }
 
-The code above is how the field tells Drupal and Tripal how to find and filter the records that this field corresponds to.  First, we retrieve the field alias and operators:and as with the load and elementInfo functions we get the controlled vocabulary terms for our field and field elements:
+The code above is how the field tells Drupal and Tripal how to find and filter the records that this field corresponds to.  First, we retrieve the field alias and operators, and as with the load and elementInfo functions we get the controlled vocabulary terms for our field and field elements:
 
 
 .. code-block:: php

docs/user_guide/install_tripal/custom_theme.rst

@@ -7,7 +7,7 @@ Drupal makes it easy to change the look-and-feel of your site by providing Theme
 
 Customizing a Theme
 -------------------
-If you want to make customizations to the theme you should create your own sub theme.  A sub theme borrows from an existing **base theme** (e.g. Bartik) and allows you to make your customizations.  Thus, when updates for a theme are released you can easily upgrade your base theme without losing your changes.   To create a sub theme, follow the instructions on the `Creating a sub-theme page <https://www.drupal.org/docs/7/theming/creating-a-sub-theme>`_ on the Drupal website.  Alternatively, completely custom themes do not borrow from any othe theme, you can create your own full-blown theme by following the `Themeing instructions <https://www.drupal.org/docs/7/theming>`_ at the Drupal website.
+If you want to make customizations to the theme you should create your own sub theme.  A sub theme borrows from an existing **base theme** (e.g. Bartik) and allows you to make your customizations.  Thus, when updates for a theme are released you can easily upgrade your base theme without losing your changes.   To create a sub theme, follow the instructions on the `Creating a sub-theme page <https://www.drupal.org/docs/7/theming/creating-a-sub-theme>`_ on the Drupal website.  Alternatively, completely custom themes do not borrow from any other theme, you can create your own full-blown theme by following the `Themeing instructions <https://www.drupal.org/docs/7/theming>`_ at the Drupal website.
 
 .. note::
 

legacy/tripal_analysis/tripal_analysis.views_default.inc

@@ -38,7 +38,7 @@ function tripal_analysis_views_default_views() {
 function tripal_analysis_defaultvalue_user_analysis() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_analysis_defaultvalue_admin_analysis();
 
   // change some view admin stuff

legacy/tripal_contact/tripal_contact.views_default.inc

@@ -37,7 +37,7 @@ function tripal_contact_views_default_views() {
 function tripal_contact_defaultvalue_user_contacts() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_contact_defaultview_admin_contacts();
 
   // change some view admin stuff

legacy/tripal_core/api/tripal_core.chado_nodes.api.inc

@@ -774,7 +774,7 @@ function chado_node_sync_form_submit($form, $form_state) {
  *   sync.
  * @param $organism_id
  *   Optional: Limit the list of records to be synced to only those that
- *   are associated with this organism_id. If the record is not assocaited
+ *   are associated with this organism_id. If the record is not associated
  *   with an organism then this field is not needed.
  * @param $types
  *   Optional: Limit the list of records to be synced to only those that

legacy/tripal_feature/theme/templates/tripal_feature_alignments.tpl.php

@@ -27,7 +27,7 @@
 *
 * Alignment context #2:
 * ---------------------
-* If the feature for this node is the child in the alignment relationsips,
+* If the feature for this node is the child in the alignment relationships,
 * then those alignments are available in this variable:
 * 
 *   $feature->featureloc->feature_id;

legacy/tripal_featuremap/tripal_featuremap.views_default.inc

@@ -35,7 +35,7 @@ function tripal_featuremap_views_default_views() {
 function tripal_featuremap_defaultvalue_user_featuremaps() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_featuremap_defaultview_admin_featuremaps();
 
   // change some view admin stuff

legacy/tripal_genetic/tripal_genetic.views_default.inc

@@ -35,7 +35,7 @@ function tripal_genetic_views_default_views() {
 function tripal_genetic_defaultvalue_user_genotypes() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_genetic_defaultviews_admin_genotypes();
 
   // change some view admin stuff

legacy/tripal_library/tripal_library.views_default.inc

@@ -35,7 +35,7 @@ function tripal_library_views_default_views() {
 function tripal_library_defaultvalue_user_library() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_library_admin_defaultviews_library();
 
   // change some view admin stuff

legacy/tripal_organism/includes/tripal_organism.chado_node.inc

@@ -688,7 +688,7 @@ function tripal_organism_node_presave($node) {
     case 'chado_organism':
       // when syncing the details are not present in the $node object
       // as they are when submitted via the form.  Therefore, if we do
-      // not see any field values from the form, we assume this fucntion
+      // not see any field values from the form, we assume this function
       // is being called for syncing, so we must set the title accordingly
       if (property_exists($node, 'genus')) {
         $node->title = $node->genus . " " . $node->species;

legacy/tripal_phenotype/tripal_phenotype.views_default.inc

@@ -35,7 +35,7 @@ function tripal_phenotype_views_default_views() {
 function tripal_phenotype_defaultvalue_user_phenotypes() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_phenotype_defaultview_admin_phenotypes();
 
   // change some view admin stuff

legacy/tripal_project/tripal_project.views_default.inc

@@ -35,7 +35,7 @@ function tripal_project_views_default_views() {
 function tripal_project_defaultvalue_user_projects() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_project_defaultview_admin_projects();
 
   // change some view admin stuff

legacy/tripal_pub/includes/tripal_pub.admin.inc

@@ -127,7 +127,7 @@ function tripal_pub_admin() {
     '#type' => 'select',
     '#title' => t('Publication Type'),
     '#options' => $pub_types,
-    '#description' => t('Please set a default publiation type used for manual entry of a new
+    '#description' => t('Please set a default publication type used for manual entry of a new
       publication.  This is useful in the event that someone is manually adding the same
       publication type repetitively'),
     '#default_value' => $d_type_id,

legacy/tripal_pub/includes/tripal_pub.chado_node.inc

@@ -1270,7 +1270,7 @@ function tripal_pub_node_presave($node) {
     case 'chado_pub':
       // when syncing the details are not present in the $node object
       // as they are when submitted via the form.  Therefore, if we do
-      // not see any field values from the form, we assume this fucntion
+      // not see any field values from the form, we assume this function
       // is being called for syncing, so we must set the title accordingly
       if (property_exists($node, 'title')) {
         // do nothing, the title is set

legacy/tripal_stock/tripal_stock.module

@@ -320,7 +320,7 @@ function tripal_stock_match_stocks_page($id) {
   if (!$url_alias) {
     $url_alias = '/stock/[genus]/[species]/[type]/[uniquename]';
   }
-  $url_alias = preg_replace('/^\//', '', $url_alias); // remove any preceeding forward slash
+  $url_alias = preg_replace('/^\//', '', $url_alias); // remove any preceding forward slash
   if (preg_match('/^stock\//', $url_alias)) {
     drupal_goto($id);
   }

legacy/tripal_stock/tripal_stock.views_default.inc

@@ -35,7 +35,7 @@ function tripal_stock_views_default_views() {
 function tripal_stock_defaultvalue_user_stocks() {
 
   // As a shortcut, currently I am copying the admin view and then tweaking it
-  // In thie future this should be replaced by a views export
+  // In the future this should be replaced by a views export
   $view = tripal_stock_defaultview_admin_stocks();
 
   // change some view admin stuff

tripal/includes/TripalEntityCollection.inc

@@ -262,7 +262,7 @@ class TripalEntityCollection {
    *
    * @return
    *   An associative array where the key is the TripalFieldDownloader class
-   *   name and the value is the human-readable lable for the formatter.
+   *   name and the value is the human-readable label for the formatter.
    */
   private function setFormatters() {
 
@@ -301,7 +301,7 @@ class TripalEntityCollection {
    *
    * @return
    *   An associative array where the key is the TripalFieldDownloader class
-   *   name and the value is the human-readable lable for the formatter.
+   *   name and the value is the human-readable label for the formatter.
    */
   public function getFormatters() {
     return $this->formatters;

tripal/includes/TripalFields/TripalField.inc

@@ -11,7 +11,7 @@ class TripalField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Tripal Field';
 
   // The default description for this field.
@@ -33,15 +33,15 @@ class TripalField {
     'searchable_keys' => [],
   ];
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'schema',
     // The name of the term.
     'term_name' => 'Thing',
@@ -518,7 +518,7 @@ class TripalField {
    * The value of this top-level key is an array with the following keys:
    *   -name: this key is not actually used but is availble to improve
    *     readability of the array.  Because the key is a vocabulary term
-   *     conaining only the accession it's not always clear what it means.
+   *     containing only the accession it's not always clear what it means.
    *     Providing a 'name' key helps other's know what the term is.
    *   -searchable:  TRUE if the element can be used for filtering the content
    *     type to which tis field is attached.  FALSE if not.

tripal/includes/TripalFields/TripalFieldFormatter.inc

@@ -3,7 +3,7 @@
 class TripalFieldFormatter {
 
   /**
-   * The default lable for this field.
+   * The default label for this field.
    */
   public static $default_label = 'Tripal Field.';
 

tripal/includes/TripalFields/TripalFieldWidget.inc

@@ -2,7 +2,7 @@
 
 class TripalFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Tripal Field.';
 
   // The list of field types for which this formatter is appropriate.
@@ -158,7 +158,7 @@ class TripalFieldWidget {
    * on other tables not directly associated with the field.
    *
    * An example is the chado.feature_synonym table.  The chado_linker__synonym
-   * field allows the user to provide a brand new synonynm and it must add it
+   * field allows the user to provide a brand new synonym and it must add it
    * to the chado.synonym table prior to the record in the
    * chado.feature_synonym table.  This insert occurs in the widgetFormSubmit
    * function.

tripal/includes/TripalFields/content_type/content_type.inc

@@ -2,7 +2,7 @@
 
 class content_type extends TripalField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Content Type';
 
   // The default description for this field.

tripal/includes/TripalFields/rdfs__type/rdfs__type.inc

@@ -2,7 +2,7 @@
 
 class rdfs__type extends TripalField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Content Type';
 
   // The default description for this field.
@@ -13,15 +13,15 @@ class rdfs__type extends TripalField {
   // Drupal will automatically change these settings for all fields.
   public static $default_settings = [];
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'rdfs',
     // The name of the term.
     'term_name' => 'type',

tripal/includes/TripalFields/rdfs__type/rdfs__type_formatter.inc

@@ -2,7 +2,7 @@
 
 class rdfs__type_formatter extends TripalFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Content Type';
 
   // The list of field types for which this formatter is appropriate.

tripal/includes/TripalFields/rdfs__type/rdfs__type_widget.inc

@@ -2,7 +2,7 @@
 
 class rdfs__type_widget extends TripalFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Content Type';
 
   // The list of field types for which this formatter is appropriate.

tripal/includes/TripalImporter.inc

@@ -47,7 +47,7 @@ class TripalImporter {
 
   /**
    * If the loader should require an analysis record.  To maintain provenance
-   * we should always indiate where the data we are uploading comes from.
+   * we should always indicate where the data we are uploading comes from.
    * The method that Tripal attempts to use for this by associating upload files
    * with an analysis record.  The analysis record provides the details for
    * how the file was created or obtained. Set this to FALSE if the loader
@@ -108,7 +108,7 @@ class TripalImporter {
 
   /**
    * Be default, all loaders are automaticlly added to the Admin >
-   * Tripal > Data Laders menu.  However, if this loader should be
+   * Tripal > Data Loaders menu.  However, if this loader should be
    * made available via a different menu path, then set it here.  If the
    * value is empty then the path will be the default.
    */
@@ -276,7 +276,7 @@ class TripalImporter {
    * to the job log.
    *
    * @param TripalJob $job
-   *   An instnace of a TripalJob.
+   *   An instance of a TripalJob.
    */
   public function setJob(TripalJob $job) {
     $this->job = $job;

tripal/includes/tripal.field_storage.inc

@@ -49,7 +49,7 @@ function tripal_field_storage_load($entity_type, $entities, $age,
       $field_type = $field['type'];
       $field_module = $field['module'];
 
-      // Get the instnace for this field
+      // Get the instance for this field
       $instance = field_info_instance($entity_type, $field_name, $entity->bundle);
 
       // Allow the creating module to alter the value if desired.  The

tripal/views_handlers/tripal_views_handler_filter_select_string.inc

@@ -142,7 +142,7 @@ class tripal_views_handler_filter_string_selectbox extends views_handler_filter_
     $placeholder_prefix = 'arg';
     $i = 0;
     foreach ($filters as $filter_name => $details) {
-      // we only want to inclue non-exposed filters
+      // we only want to include non-exposed filters
       if ($details->options['exposed'] == FALSE) {
         $i++;
 

tripal_bulk_loader/api/tripal_bulk_loader.api.templates.inc

@@ -38,7 +38,7 @@
  *   value is the error message.
  *
  * @return
- *   If validation failes then FALSE is returned.  Any options that do not pass
+ *   If validation fails then FALSE is returned.  Any options that do not pass
  *   validation checks will be added in the $errors array with the key being
  *   the option and the value being the error message.  If validation
  *   is successful then TRUE is returned.

tripal_chado/api/modules/tripal_chado.analysis.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing analysis records in Chado.
+ * Provides API functions specifically for managing analysis records in Chado.
  *
  * @ingroup tripal_chado
  */
@@ -19,7 +19,7 @@
 /**
  * Retrieves a chado analysis variable.
  *
- * @param $itentifier
+ * @param $identifier
  *   an array with the key stating what the identifier is. Supported keys
  *   (only on of the following unique keys is required):
  *    - analysis_id: the chado analysis.analysis_id primary key.

tripal_chado/api/modules/tripal_chado.contact.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing contact records in Chado.
+ * Provides API functions specifically for managing contact records in Chado.
  *
  * @ingroup tripal_chado
  */

tripal_chado/api/modules/tripal_chado.cv.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing controlled vocabulary
+ * Provides API functions specifically for managing controlled vocabulary
  * records in Chado.
  *
  * @ingroup tripal_chado
@@ -11,7 +11,7 @@
  * @defgroup tripal_chado_cv_api Chado CV
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing controlled vocabulary
+ * Provides API functions specifically for managing controlled vocabulary
  * records in Chado. Please note that Tripal v3 provides a generic set of
  * API functions for working with controlled vocabularies (CVs). This allows for
  * CVs to be stored using any back-end.  By default CV's continue to be housed

tripal_chado/api/modules/tripal_chado.db.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing external database reference
+ * Provides API functions specifically for managing external database reference
  * records in Chado.
  */
 

tripal_chado/api/modules/tripal_chado.feature.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing feature
+ * Provides API functions specifically for managing feature
  * records in Chado.
  */
 
@@ -9,7 +9,7 @@
  * @defgroup tripal_feature_api Chado Feature
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing feature
+ * Provides API functions specifically for managing feature
  * records in Chado especially retrieving relationships and sequences derived
  * from relationships and feature alignments.
  * @}
@@ -120,7 +120,7 @@ function chado_reverse_compliment_sequence($sequence) {
  *   sequence_of)
  *      then any sequences that are in relationships of this type with matched
  *      sequences are also included.
- *    - relationship_part: If a relationship is provided in the preceeding
+ *    - relationship_part: If a relationship is provided in the preceding
  *      argument then the rel_part must be either 'object' or 'subject' to
  *      indicate which side of the relationship the matched features belong.
  *
@@ -435,7 +435,7 @@ function chado_get_feature_sequences($feature, $options) {
           }
 
           // Next, if the last sub feature we need to include the downstream
-          // bases. First check if the feature is in teh forward direction or
+          // bases. First check if the feature is in the forward direction or
           // the reverse.
           elseif ($i == $num_children - 1 and $parent->strand >= 0) {  // forward direction
             // -------------------------- ref
@@ -609,7 +609,7 @@ function chado_get_feature_sequences($feature, $options) {
  *   sequence_of)
  *      then any sequences that are in relationships of this type with matched
  *      sequences are also included
- *    - relationship_part: If a relationship is provided in the preceeding
+ *    - relationship_part: If a relationship is provided in the preceding
  *      argument then the rel_part must be either 'object' or 'subject' to
  *      indicate which side of the relationship the matched features belong
  *    - width: Indicate the number of bases to use per line.  A new line will

tripal_chado/api/modules/tripal_chado.module.DEPRECATED.api.inc

@@ -20,7 +20,7 @@
 /**
  * Retrieves a chado analysis variable.
  *
- * @param $itentifier
+ * @param $identifier
  *   an array with the key stating what the identifier is. Supported keys
  *   (only on of the following unique keys is required):
  *    - analysis_id: the chado analysis.analysis_id primary key.
@@ -726,7 +726,7 @@ function tripal_reverse_compliment_sequence($sequence) {
  *   sequence_of)
  *      then any sequences that are in relationships of this type with matched
  *      sequences are also included.
- *    - relationship_part: If a relationship is provided in the preceeding
+ *    - relationship_part: If a relationship is provided in the preceding
  *      argument then the rel_part must be either 'object' or 'subject' to
  *      indicate which side of the relationship the matched features belong.
  *
@@ -782,7 +782,7 @@ function tripal_get_feature_sequences($feature, $options) {
  *   sequence_of)
  *      then any sequences that are in relationships of this type with matched
  *      sequences are also included
- *    - relationship_part: If a relationship is provided in the preceeding
+ *    - relationship_part: If a relationship is provided in the preceding
  *      argument then the rel_part must be either 'object' or 'subject' to
  *      indicate which side of the relationship the matched features belong
  *    - width: Indicate the number of bases to use per line.  A new line will
@@ -995,7 +995,7 @@ function tripal_abbreviate_infraspecific_rank($rank) {
  *   value is the error message.
  *
  * @return
- *   If validation failes then FALSE is returned.  Any options that do not pass
+ *   If validation fails then FALSE is returned.  Any options that do not pass
  *   validation checks will be added in the $errors array with the key being
  *   the option and the value being the error message.  If validation
  *   is successful then TRUE is returned.
@@ -1166,7 +1166,7 @@ function tripal_assign_phylogeny_tree_indices(&$tree, &$index = 1) {
  *   -organism_id:  The organism_id for associtating the node with an organism.
  *   -properties:   An array of key/value pairs where the key is the cvterm_id
  *                  and the value is the property value.  These properties
- *                  will be assocaited with the phylonode.
+ *                  will be associated with the phylonode.
  *
  * Prior to importing the tree the indicies can be set by using the
  * chado_assign_phylogeny_tree_indices() function.
@@ -1292,7 +1292,7 @@ function tripal_get_publication($identifiers, $options = []) {
 
 /**
  * The publication table of Chado only has a unique constraint for the
- * uniquename of the publiation, but in reality a publication can be considered
+ * uniquename of the publication, but in reality a publication can be considered
  * unique by a combination of the title, publication type, published year and
  * series name (e.g. journal name or conference name). The site administrator
  * can configure how publications are determined to be unique.  This function

tripal_chado/api/modules/tripal_chado.organism.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing feature
+ * Provides API functions specifically for managing feature
  * records in Chado.
  */
 
@@ -9,7 +9,7 @@
  * @defgroup tripal_organism_api Chado Organism
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing organism
+ * Provides API functions specifically for managing organism
  * records in Chado.
  * @}
  */

tripal_chado/api/modules/tripal_chado.phylotree.api.inc

@@ -2,7 +2,7 @@
 
 /**
  * @file
- * Provides API functions specificially for managing phylogenetic and taxonomic
+ * Provides API functions specifically for managing phylogenetic and taxonomic
  * tree records in Chado.
  */
 
@@ -10,7 +10,7 @@
  * @defgroup tripal_phylotree_api Chado Phylotree
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing phylogenetic and taxonomic
+ * Provides API functions specifically for managing phylogenetic and taxonomic
  * tree records in Chado.  The API consists of functions for creation,
  * retrieval, update and deltion (CRUD) for phylogenetic tree records as
  * well as importing of trees in the newick file format.
@@ -44,7 +44,7 @@
  *   value is the error message.
  *
  * @return
- *   If validation failes then FALSE is returned.  Any options that do not pass
+ *   If validation fails then FALSE is returned.  Any options that do not pass
  *   validation checks will be added in the $errors array with the key being
  *   the option and the value being the error message.  If validation
  *   is successful then TRUE is returned.
@@ -619,7 +619,7 @@ function chado_assign_phylogeny_tree_indices(&$tree, &$index = 1) {
  *   -organism_id:  The organism_id for associtating the node with an organism.
  *   -properties:   An array of key/value pairs where the key is the cvterm_id
  *                  and the value is the property value.  These properties
- *                  will be assocaited with the phylonode.
+ *                  will be associated with the phylonode.
  *
  * Prior to importing the tree the indicies can be set by using the
  * chado_assign_phylogeny_tree_indices() function.
@@ -745,7 +745,7 @@ function chado_phylogeny_import_tree(&$tree, $phylotree, $options, $vocab = [],
     $phylonode = chado_insert_record('phylonode', $values);
     $tree['phylonode_id'] = $phylonode['phylonode_id'];
 
-    // This is a taxonomic tree, so assocaite this node with an
+    // This is a taxonomic tree, so associate this node with an
     // organism if one is provided.
     if (array_key_exists('organism_id', $tree)) {
       $values = [

tripal_chado/api/modules/tripal_chado.project.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing project
+ * Provides API functions specifically for managing project
  * records in Chado.
  */
 
@@ -9,7 +9,7 @@
  * @defgroup tripal_project_api Chado Project
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing project
+ * Provides API functions specifically for managing project
  * records in Chado.  The project table of Chado is used for storing a variety
  * of data types besides just projects from a project collection.  Examples of
  * other records commonly stored in the project table are germplasm and

tripal_chado/api/modules/tripal_chado.pub.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing publication
+ * Provides API functions specifically for managing publication
  * records in Chado.
  */
 
@@ -9,7 +9,7 @@
  * @defgroup tripal_pub_api Chado Publication
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing publication
+ * Provides API functions specifically for managing publication
  * records in Chado.
  * @}
  */
@@ -156,7 +156,7 @@ function chado_get_publication($identifiers, $options = []) {
 
 /**
  * The publication table of Chado only has a unique constraint for the
- * uniquename of the publiation, but in reality a publication can be considered
+ * uniquename of the publication, but in reality a publication can be considered
  * unique by a combination of the title, publication type, published year and
  * series name (e.g. journal name or conference name). The site administrator
  * can configure how publications are determined to be unique.  This function

tripal_chado/api/modules/tripal_chado.stock.api.inc

@@ -1,7 +1,7 @@
 <?php
 /**
  * @file
- * Provides API functions specificially for managing stock
+ * Provides API functions specifically for managing stock
  * records in Chado.
  */
 
@@ -9,7 +9,7 @@
  * @defgroup tripal_stock_api Chado Stock
  * @ingroup tripal_chado_api
  * @{
- * Provides API functions specificially for managing stock
+ * Provides API functions specifically for managing stock
  * records in Chado.  The stock table of Chado is used for storing a variety
  * of data types besides just stocks from a stock collection.  Examples of
  * other records commonly stored in the stock table are germplasm and

tripal_chado/api/tripal_chado.variables.api.inc

@@ -41,7 +41,7 @@
  *   $feature = chado_generate_var('feature', $values);
  * @endcode
  *
- * The $values array passed to this fucntion can be of the same format used
+ * The $values array passed to this function can be of the same format used
  * by the chado_select_record() function.
  *
  * If a field is a foreign key then its value is an object that contains

tripal_chado/includes/TripalFields/ChadoField.inc

@@ -2,7 +2,7 @@
 
 class ChadoField extends TripalField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Chado Field';
 
   // The default description for this field.
@@ -17,15 +17,15 @@ class ChadoField extends TripalField {
     'storage' => 'field_chado_storage',
   ];
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'schema',
     // The name of the term.
     'term_name' => 'Thing',

tripal_chado/includes/TripalFields/chado_linker__contact/chado_linker__contact.inc

@@ -11,22 +11,22 @@ class chado_linker__contact extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contacts';
 
   // The default description for this field.
   public static $description = 'Associates an indviddual or organization with
           this record';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'local',
     // The name of the term.
     'term_name' => 'contact',

tripal_chado/includes/TripalFields/chado_linker__contact/chado_linker__contact_formatter.inc

@@ -2,7 +2,7 @@
 
 class chado_linker__contact_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contacts';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/chado_linker__contact/chado_linker__contact_widget.inc

@@ -2,7 +2,7 @@
 
 class chado_linker__contact_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contacts';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/chado_linker__prop/chado_linker__prop.inc

@@ -11,21 +11,21 @@ class chado_linker__prop extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Chado Property';
 
   // The default description for this field.
   public static $description = 'Add details about this property.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'local',
     // The name of the term.
     'term_name' => 'property',

tripal_chado/includes/TripalFields/chado_linker__prop/chado_linker__prop_formatter.inc

@@ -2,7 +2,7 @@
 
 class chado_linker__prop_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Chado Property';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/chado_linker__prop/chado_linker__prop_widget.inc

@@ -2,7 +2,7 @@
 
 class chado_linker__prop_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Chado Property';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__accession/data__accession.inc

@@ -11,21 +11,21 @@ class data__accession extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Site Accession';
 
   // The default description for this field.
   public static $description = 'The unique stable accession (ID) for this record on this site.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'accession',

tripal_chado/includes/TripalFields/data__accession/data__accession_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__accession_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Site Accession';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__accession/data__accession_widget.inc

@@ -2,7 +2,7 @@
 
 class data__accession_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Site Accession';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__protein_sequence/data__protein_sequence.inc

@@ -11,21 +11,21 @@ class data__protein_sequence extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Protein Sequence';
 
   // The default description for this field.
   public static $description = 'polypeptide sequences.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'protein_sequence',

tripal_chado/includes/TripalFields/data__protein_sequence/data__protein_sequence_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__protein_sequence_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Protein Sequence';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__protein_sequence/data__protein_sequence_widget.inc

@@ -2,7 +2,7 @@
 
 class data__protein_sequence_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Protein Sequence';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence/data__sequence.inc

@@ -11,21 +11,21 @@ class data__sequence extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence';
 
   // The default description for this field.
   public static $description = 'A field for managing nucleotide and protein residues.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'sequence',

tripal_chado/includes/TripalFields/data__sequence/data__sequence_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence/data__sequence_widget.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_checksum/data__sequence_checksum.inc

@@ -11,21 +11,21 @@ class data__sequence_checksum extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence checksum';
 
   // The default description for this field.
   public static $description = 'A field for generating MD5 checksum for a sequence.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'sequence_checksum',

tripal_chado/includes/TripalFields/data__sequence_checksum/data__sequence_checksum_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_checksum_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence checksum';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_checksum/data__sequence_checksum_widget.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_checksum_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence checksum';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_coordinates/data__sequence_coordinates.inc

@@ -11,21 +11,21 @@ class data__sequence_coordinates extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence Coordinates';
 
   // The default description for this field.
   public static $description = 'Locations on reference sequences where the feature is located.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'sequence_coordinates',

tripal_chado/includes/TripalFields/data__sequence_coordinates/data__sequence_coordinates_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_coordinates_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence Coordinate List';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_coordinates/data__sequence_coordinates_widget.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_coordinates_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence Coordinates';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_coordinates_table/data__sequence_coordinates_table_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_coordinates_table_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence Coordinate Table';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_length/data__sequence_length.inc

@@ -12,21 +12,21 @@ class data__sequence_length extends ChadoField {
   // --------------------------------------------------------------------------
 
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence length';
 
   // The default description for this field.
   public static $description = 'A field for calculating the length of a sequence.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'data',
     // The name of the term.
     'term_name' => 'sequence_length',

tripal_chado/includes/TripalFields/data__sequence_length/data__sequence_length_formatter.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_length_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence length';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/data__sequence_length/data__sequence_length_widget.inc

@@ -2,7 +2,7 @@
 
 class data__sequence_length_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Sequence length';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/efo__array_design/efo__array_design.inc

@@ -2,21 +2,21 @@
 
 class efo__array_design extends ChadoField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Array Design';
 
   // The default description for this field.
   public static $description = 'An instrument design which describes the design of the array.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'EFO',
     // The name of the term.
     'term_name' => 'array design',

tripal_chado/includes/TripalFields/efo__array_design/efo__array_design_formatter.inc

@@ -2,7 +2,7 @@
 
 class efo__array_design_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Array Design';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/efo__array_design/efo__array_design_widget.inc

@@ -2,7 +2,7 @@
 
 class efo__array_design_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Array Design';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/go__gene_expression/go__gene_expression.inc

@@ -11,7 +11,7 @@ class go__gene_expression extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Gene expression';
 
   // The default description for this field.
@@ -22,15 +22,15 @@ class go__gene_expression extends ChadoField {
       Protein maturation is included when required to form an active form of a product from
       an inactive precursor form.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'GO',
     // The name of the term.
     'term_name' => 'gene expression',

tripal_chado/includes/TripalFields/go__gene_expression/go__gene_expression_formatter.inc

@@ -2,7 +2,7 @@
 
 class go__gene_expression_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Gene expression';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/go__gene_expression/go__gene_expression_widget.inc

@@ -2,7 +2,7 @@
 
 class go__gene_expression_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Gene expression';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/local__contact/local__contact.inc

@@ -11,21 +11,21 @@ class local__contact extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contact';
 
   // The default description for this field.
   public static $description = 'An indviddual or organization that serves as a contact for this record.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'local',
     // The name of the term.
     'term_name' => 'contact',

tripal_chado/includes/TripalFields/local__contact/local__contact_formatter.inc

@@ -2,7 +2,7 @@
 
 class local__contact_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contact';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/local__contact/local__contact_widget.inc

@@ -2,7 +2,7 @@
 
 class local__contact_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Contact';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/local__source_data/local__source_data.inc

@@ -11,21 +11,21 @@ class local__source_data extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Source of Data';
 
   // The default description for this field.
   public static $description = 'The source data used for this analysis.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'local',
     // The name of the term.
     'term_name' => 'source_data',

tripal_chado/includes/TripalFields/local__source_data/local__source_data_formatter.inc

@@ -2,7 +2,7 @@
 
 class local__source_data_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Data Source';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/local__source_data/local__source_data_widget.inc

@@ -2,7 +2,7 @@
 
 class local__source_data_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Data Source';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/obi__organism/obi__organism.inc

@@ -2,21 +2,21 @@
 
 class obi__organism extends ChadoField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Organism';
 
   // The default description for this field.
   public static $description = 'The organism to which this resource is associated.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'OBI',
     // The name of the term.
     'term_name' => 'organism',

tripal_chado/includes/TripalFields/obi__organism/obi__organism_formatter.inc

@@ -2,7 +2,7 @@
 
 class obi__organism_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Organism';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/obi__organism/obi__organism_widget.inc

@@ -2,7 +2,7 @@
 
 class obi__organism_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Organism';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/ogi__location_on_map/ogi__location_on_map.inc

@@ -11,21 +11,21 @@ class ogi__location_on_map extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Location on Map';
 
   // The default description for this field.
   public static $description = 'Map position of a sequence.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'OGI',
     // The name of the term.
     'term_name' => 'location on map',

tripal_chado/includes/TripalFields/ogi__location_on_map/ogi__location_on_map_formatter.inc

@@ -2,7 +2,7 @@
 
 class ogi__location_on_map_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Location on Map';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/ogi__location_on_map/ogi__location_on_map_widget.inc

@@ -2,7 +2,7 @@
 
 class ogi__location_on_map_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Location on Map';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/operation__analysis/operation__analysis.inc

@@ -2,21 +2,21 @@
 
 class operation__analysis extends ChadoField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Analysis';
 
   // The default description for this field.
   public static $description = 'Application of analytical methods to existing data of a specific type.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'operation',
     // The name of the term.
     'term_name' => 'Analysis',

tripal_chado/includes/TripalFields/operation__analysis/operation__analysis_formatter.inc

@@ -2,7 +2,7 @@
 
 class operation__analysis_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Analysis';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/operation__analysis/operation__analysis_widget.inc

@@ -2,7 +2,7 @@
 
 class operation__analysis_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Analysis';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/operation__phylotree_vis/operation__phylotree_vis.inc

@@ -2,21 +2,21 @@
 
 class operation__phylotree_vis extends ChadoField {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phylogenetic tree visualisation';
 
   // The default description for this field.
   public static $description = 'Rendering of a phylogenetic tree.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'operation',
     // The name of the term.
     'term_name' => 'Phylogenetic tree visualisation',

tripal_chado/includes/TripalFields/operation__phylotree_vis/operation__phylotree_vis_formatter.inc

@@ -2,7 +2,7 @@
 
 class operation__phylotree_vis_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phylogenetic tree visualisation';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/operation__phylotree_vis/operation__phylotree_vis_widget.inc

@@ -2,7 +2,7 @@
 
 class operation__phylotree_vis_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phylogenetic tree visualisation';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/sbo__database_cross_reference/sbo__database_cross_reference.inc

@@ -11,7 +11,7 @@ class sbo__database_cross_reference extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Cross reference';
 
   // The default description for this field.
@@ -19,15 +19,15 @@ class sbo__database_cross_reference extends ChadoField {
           another online database. This field is intended for one or more
           references.  At a minimum, the database and accession must be provided.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'SBO',
     // The name of the term.
     'term_name' => 'Database Cross Reference',

tripal_chado/includes/TripalFields/sbo__database_cross_reference/sbo__database_cross_reference_formatter.inc

@@ -2,7 +2,7 @@
 
 class sbo__database_cross_reference_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Cross reference';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/sbo__database_cross_reference/sbo__database_cross_reference_widget.inc

@@ -2,7 +2,7 @@
 
 class sbo__database_cross_reference_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Cross reference';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/sbo__phenotype/sbo__phenotype.inc

@@ -11,7 +11,7 @@ class sbo__phenotype extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phenotype';
 
   // The default description for this field.
@@ -19,15 +19,15 @@ class sbo__phenotype extends ChadoField {
       biological processes. Such processes can take place at different levels and are
       independent of the biochemical network itself.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'SBO',
     // The name of the term.
     'term_name' => 'Phenotype',

tripal_chado/includes/TripalFields/sbo__phenotype/sbo__phenotype_formatter.inc

@@ -2,7 +2,7 @@
 
 class sbo__phenotype_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phenotype';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/sbo__phenotype/sbo__phenotype_widget.inc

@@ -2,7 +2,7 @@
 
 class sbo__phenotype_widget extends ChadoFieldWidget {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Phenotype';
 
   // The list of field types for which this formatter is appropriate.

tripal_chado/includes/TripalFields/sbo__relationship/sbo__relationship.inc

@@ -11,21 +11,21 @@ class sbo__relationship extends ChadoField {
   // the field and it's default widget and formatter.
   // --------------------------------------------------------------------------
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Relationship';
 
   // The default description for this field.
   public static $description = 'Relationships between records.';
 
-  // Provide a list of instance specific settings. These can be access within
+  // Provide a list of instance specific settings. These can be accessed within
   // the instanceSettingsForm.  When the instanceSettingsForm is submitted
-  // then Drupal with automatically change these settings for the instnace.
+  // then Drupal will automatically change these settings for the instance.
   // It is recommended to put settings at the instance level whenever possible.
   // If you override this variable in a child class be sure to replicate the
   // term_name, term_vocab, term_accession and term_fixed keys as these are
   // required for all TripalFields.
   public static $default_instance_settings = [
-    // The short name for the vocabulary (e.g. shcema, SO, GO, PATO, etc.).
+    // The short name for the vocabulary (e.g. schema, SO, GO, PATO, etc.).
     'term_vocabulary' => 'SBO',
     // The name of the term.
     'term_name' => 'Relationship',
@@ -309,7 +309,7 @@ class sbo__relationship extends ChadoField {
       'schema:name' => implode(' ', $name),
     ];
 
-    // If the object has a uniquename then add that in for refernce.
+    // If the object has a uniquename then add that in for reference.
     if (property_exists($relationship->{$this->subject_id_column}, 'uniquename')) {
       $record['data:0842'] = $relationship->{$this->subject_id_column}->uniquename;
     }

tripal_chado/includes/TripalFields/sbo__relationship/sbo__relationship_formatter.inc

@@ -2,7 +2,7 @@
 
 class sbo__relationship_formatter extends ChadoFieldFormatter {
 
-  // The default lable for this field.
+  // The default label for this field.
   public static $default_label = 'Relationship Statements';
 
   // The list of field types for which this formatter is appropriate.