Apply suggestions from code review

Co-authored-by: Gavin King <[email protected]>

Author: yrodiere

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, implement a custom generator by extending the OnExecutionGenerator interface, and apply it to the version attribute using a custom annotation. Refer to the Hibernate documentation for the latest guidelines on handling database-managed attributes.
+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,7 +41,7 @@ which means that accessing `accountsPayableXrefId` will not force the loading of
 
 [NOTE]
 ====
-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)`.
+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]]