Updated Drupal to 8.6. This goes with the following updates because it's possible...

[yaffs-website] / web / core / lib / Drupal / Core / Form / FormState.php

diff --git a/web/core/lib/Drupal/Core/Form/FormState.php b/web/core/lib/Drupal/Core/Form/FormState.php
index 5585a76234e60796cea0452b29d418c43f54a252..8264371c832deda8aa65f2edbe1ca77fc524371a 100644 (file)
--- a/web/core/lib/Drupal/Core/Form/FormState.php
+++ b/web/core/lib/Drupal/Core/Form/FormState.php
@@ -87,8 +87,8 @@ class FormState implements FormStateInterface {
    * copy of the form is immediately built and sent to the browser, instead of a
    * redirect. This is used for multi-step forms, such as wizards and
    * confirmation forms. Normally, self::$rebuild is set by a submit handler,
-   * since its is usually logic within a submit handler that determines whether
-   * a form is done or requires another step. However, a validation handler may
+   * since it is usually logic within a submit handler that determines whether a
+   * form is done or requires another step. However, a validation handler may
    * already set self::$rebuild to cause the form processing to bypass submit
    * handlers and rebuild the form instead, even if there are no validation
    * errors.
@@ -609,13 +609,13 @@ class FormState implements FormStateInterface {
   /**
    * Checks whether the request method is a "safe" HTTP method.
    *
-   * http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1 defines
-   * GET and HEAD as "safe" methods, meaning they SHOULD NOT have side-effects,
-   * such as persisting $form_state changes.
+   * Link below defines GET and HEAD as "safe" methods, meaning they SHOULD NOT
+   * have side-effects, such as persisting $form_state changes.
    *
    * @return bool
    *
    * @see \Symfony\Component\HttpFoundation\Request::isMethodSafe()
+   * @see http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1
    */
   protected function isRequestMethodSafe() {
     return in_array($this->requestMethod, ['GET', 'HEAD']);