(grails-core) 04/06: cleanup: formatting for documentation

[jd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jdaugherty pushed a commit to branch feature/exploded
in repository https://gitbox.apache.org/repos/asf/grails-core.git

commit 64db3e78622e8cf2e74cc7d5944c94e1bf41e747
Author: James Daugherty <jd...@jdresources.net>
AuthorDate: Wed Sep 17 08:49:23 2025 -0400

    cleanup: formatting for documentation
---
 grails-doc/src/en/guide/upgrading/upgrading60x.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/grails-doc/src/en/guide/upgrading/upgrading60x.adoc b/grails-doc/src/en/guide/upgrading/upgrading60x.adoc
index 7e60517372..57ccd1435e 100644
--- a/grails-doc/src/en/guide/upgrading/upgrading60x.adoc
+++ b/grails-doc/src/en/guide/upgrading/upgrading60x.adoc
@@ -489,4 +489,6 @@ Alternatively, you can define the hibernate-ehcache dependency explicitly and ad
 In previous versions of Grails, it was possible to apply both the `grails-plugin` and `grails-web` Gradle plugins in `build.gradle`.
 This would force the project to be both a Grails Plugin and a Grails Application.
 This scenario is not supported and can lead to unexpected behavior due to the AST transforms.
-Starting with Grails 7, a validation error will trigger if both of these plugins are configured in `build.gradle` for the same Gradle Project.
+
+Starting with Grails 7, a validation error will trigger if both a Grails Application Gradle Plugin & a Grails Plugin Gradle Plugin are configured in `build.gradle` for the same Gradle Project.
+