HHH-18993 Fix outdated information in user guide

Co-authored-by: Gavin King <gavin@hibernate.org>

Author: 2 people

documentation/src/main/asciidoc/userguide/chapters/locking/Locking.adoc

@@ -96,7 +96,7 @@ To artificially increase the version number, see the documentation for propertie
 
 [NOTE]
 ====
-If the version number is generated by the database, such as a trigger, use the annotation `@org.hibernate.annotations.Generated(GenerationTime.ALWAYS)` on the version attribute.
+If the version number is generated by the database, such as a trigger, implement a custom generator by extending the `OnExecutionGenerator` interface, and apply it to the version attribute using a custom annotation.
 ====
 
 [[locking-optimistic-timestamp]]

documentation/src/main/asciidoc/userguide/chapters/pc/BytecodeEnhancement.adoc

@@ -41,8 +41,7 @@ which means that accessing `accountsPayableXrefId` will not force the loading of
 
 [NOTE]
 ====
-As a hopefully temporary legacy hold-over, it is currently required that all lazy singular associations (many-to-one and one-to-one) also include `@LazyToOne(LazyToOneOption.NO_PROXY)`.
-The plan is to relax that requirement later.
+For existing codebases, it is recommended to remove usages of @LazyToOne, such as `@LazyToOne(LazyToOneOption.NO_PROXY)`, and instead rely on default lazy loading behavior or explicitly configure fetch strategies using `@OneToOne` or `@ManyToOne` annotations with `fetch = FetchType.LAZY` where necessary, such as `@OneToOne(fetch = FetchType.LAZY)`.
 ====
 
 [[BytecodeEnhancement-dirty-tracking]]

documentation/src/main/asciidoc/userguide/chapters/pc/PersistenceContext.adoc

@@ -229,7 +229,7 @@ strategy so that we can load entities from the second-level cache, therefore ski
 `withBatchSize(int batchSize)`::
 This setting allows you to specify a batch size for loading the entities (e.g. how many at a time).
 +
-The default is to use a batch sizing strategy defined by the `Dialect.getDefaultBatchLoadSizingStrategy()` method.
+The default is to use a batch sizing strategy defined by the `Dialect.getBatchLoadSizingStrategy()` method.
 +
 Any greater-than-one value here will override that default behavior.
 `with(RootGraph<T> graph)`::