Errata

Looks like "way" or "manner" is missing from the following sentence: "A measurement error or an unconnected factor affects results in an uncorrelated."

"The klass word is used to locate the klass metatdata (or klass)". Remove last t from "metat"

The "Family name" column is not wide enough so the last letter of lookupswitch jumps to the next line

"Application" is misspelled "appliction" here:

"Historically, the JVM required the developer to choose between the C1 and C2 compilers at appliction startup time"

I'm not sure if this a poor sentence or a typo - I find it hard to make sense of even with the potential correction, but I think "segmentation" should have been "segments" (as a verb).

"The code cache segmentation groups by compiled code types, closely tied to lifetime, helping to prevent the fragmentation effects and associated sweeps and collections."

"Optimized" misspelled here: "Profiled code heap, which contains lightly opimized compiled code"

Opening parenthesis is never matched by a close parenthesis: "This is similar to how a logging framework operates (i.e., both are examples of the facade pattern."

I believe the array of primitives type should be typeArrayOop, not objArrayOop

"The basic overall inheritance hierarchy for oops looks like this (as of Java 22):

oop (abstract base)
instanceOop (instance objects)
stackChunkOop
arrayOop (array abstract base)
objArrayOop (array object)
objArrayOop (array of primitives)"

"By" should be "be" in "may even by submillisecond."

"Compatibility" is misspelled in: "OTel places great emphasis on stability and backward compatability"

"Called" misspelled in "what is sometimes caled a lift-and-shift approach"

Text describes code as a "do loop". This type of loop is usually refered to as a "do while loop".

"uses a simple do loop to keep selecting a random cat until we choose one that is uninjured (i.e., is not in the cache maintained by the hospital service)."

"Still" is misspelled "sill" in
"but it sill should not be done if not necessary."

Opening parenthesis is never matched by a closing parenthesis:

"In particular, Java Microbenchmark Harness (JMH tests would benefit from the ability to confidently exclude any GC events from disrupting performance numbers. Memory allocation regression tests, ensuring that changed code does not greatly alter allocation behavior, would also become easy to do."