From ee47bc3a25cb1c38d0666a685a8a6b4255daa325 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Rowicki?= Date: Mon, 12 Aug 2019 11:21:54 +0200 Subject: [PATCH] Fix typo in data access reference documentation Closes gh-23450 --- src/docs/asciidoc/data-access.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/asciidoc/data-access.adoc b/src/docs/asciidoc/data-access.adoc index afddd69af1f..0e24d53e34f 100644 --- a/src/docs/asciidoc/data-access.adoc +++ b/src/docs/asciidoc/data-access.adoc @@ -5737,7 +5737,7 @@ generic or customized to various platforms (such as Tomcat, JBoss and WebSphere) As described in <>, you can configure a context-wide `LoadTimeWeaver` by using the `@EnableLoadTimeWeaving` annotation of the -`context:load-time-weaver` XML element. Such a global weaver is automatically picked u +`context:load-time-weaver` XML element. Such a global weaver is automatically picked up by all JPA `LocalContainerEntityManagerFactoryBean` instances. The following example shows the preferred way of setting up a load-time weaver, delivering auto-detection of the platform (e.g. Tomcat's weaving-capable class loader or Spring's JVM agent)