Edit hook_help text for Field Layout module

Fixing event tag :p

Made some changes according to Help text standards.

Sorry about the last patch. Missed semi colon.

@dhruveshdtripathi, Thanks for the updated patch, it works well. I checked it via simplytest.me & also attached the images of results.

Have made the changes as suggested. Please review .

Is there only an interdiff needed or any other issues?

Have attached the interdiff file for the above patch.

Any updates with this issue?

+++ b/core/modules/field_layout/field_layout.module
@@ -23,12 +23,13 @@
-      $output .= '<p>' . t('For more information, see the <a href=":field-layout-documentation">online documentation for the Field Layout module</a>.', [':field-layout-documentation' => 'https://www.drupal.org/documentation/modules/field_layout']) . '</p>';
...
+      $output .= '<p>' . t('For more information, see the <a href=":field-layout-documentation">online documentation for the Field Layout module</a>.', [':field-layout-documentation' => 'https://www.drupal.org/project/fieldlayout']) . '</p>';

This is an incorrect change, this core module has nothing to do with https://www.drupal.org/project/fieldlayout

Adding updated patch based on previous comments and few minor corrections.

+++ b/core/modules/field_layout/field_layout.module
@@ -26,6 +26,10 @@ function field_layout_help($route_name, RouteMatchInterface $route_match) {
+      $output .= '<p>' . t('Field layout defines 9 default regions (top, float-left, float-right, body, bottom, etc.) into which node fields can be placed') . '</p>';
+      $output .= '<p>' . t('Layouts can also be changed dynamically in your themes node_preprocess hook to allow layouts to react to the node contents.') . '</p>';

Neither of these statements are true either :(

I'm very confused as to where this information is coming from?

I'm looking at this one at DrupalCon Vienna under a mentored sprint.

I had a word with @tim.plunkett at DC Vienna and we've decided to postpone working on it as of now as it's still in experimental stage and we're not really sure about the best practical Uses of Field Layout module yet.

Henceforth, we can't put the accurate "Uses" text in help section as of now.

While we're on the topic, I'd also like to mention that the module "fieldlayout" is not same as the core "field_layout" module and probably this is the major reason of all the confusion and wrong patches.

"fieldlayout" is not the core module and both the modules work differently. Please take care of the same in future patches. :)

Tagging for our future work, and assigning to myself.

Sorry for the confusion everyone! And thanks @rakesh_verma and @ifrik.

This was an issue during an documentation triage session. Field Layout is to be removed from core so I am moving this to that component. When the module is moved this can then go with it to contrib.

#3007167: [META] Enable layout builder for form displays, and deprecate field_layout

Thanks @quietone