Typos in various articles (multi-article typo only ticket)

Hello dev.java team!

Thanks again for all the content. I have been reporting issues as a way to contribute back, and when I can I try to give deep feedback on various issues (like mismatched or missing links, non-compiling code, error cases in examples, conceptual issues if they are present which is rare, etc) with 1 ticket per page or tutorial series. However, even when I don't have the bandwidth to do such a deep review of a page when reporting anything, I often notice typos in articles. Thus I am opening this ticket to report simple spelling errors I identify across many articles where I don't have time (yet) to review the entire content of those articles deeply but am aware of typos.

(There were no AIs or LLMs used in finding or reporting these typos.)

In the latest version of https://dev.java/learn/language-basics/arrays/ (archived as is at http://web.archive.org/web/20260714060411/https://dev.java/learn/language-basics/arrays/ ),

"Frappucino" is written in the code examples and expected output; I think this should be Frappuccino ( https://en.wikipedia.org/w/index.php?title=Frappuccino&oldid=1360238213 )
In the example

String[] coffees = {
 "Affogato", "Americano", "Cappuccino", "Corretto", "Cortado",
 "Doppio", "Espresso", "Frappucino", "Freddo", "Lungo", "Macchiato",
  "Marocchino", "Ristretto" };

var coffeesAsString = Arrays.toString(coffees)
IO.prinln(coffeesAsString);

the code box will not run for multiple reasons:
"Arrays.toString(coffees)" is missing an ending semicolon afterwards;
"IO.prinln" should be "IO.println" (there is a missing "t").

also,
"Frappucino" should be "Frappuccino" ( https://en.wikipedia.org/w/index.php?title=Frappuccino&oldid=1360238213 ).

In the sentence,

Note that this method has several overloads to accomodate for the arrays of primitive types.

"accomodate" should be "accommodate".

In the latest version of https://dev.java/learn/pattern-matching/ (archived as is at https://web.archive.org/web/20260714011718/https://dev.java/learn/pattern-matching/ ) ,

In the sentence

The s pattern variable is available oustide of the if statement, as long as your code leaves the method from the if branch: either with a return, or by throwing an exception.

"oustide" should be "outside". Also this statement is unclear. The condition of the if is true if o is NOT an instanceof String, so the pattern variable is available if the condition is false; in the branch where the if is bypassed, not hitting the return (this is true because if the IF is bypassed it means o must have been a string, this would also be true if the return was replaced with throwing an exception).
In the sentence

For that, let us consider the folowing example.

"folowing" should be "following".

In the latest version of https://dev.java/learn/annotations/ (archived as is at https://web.archive.org/web/20260714032443/https://dev.java/learn/annotations/?nonce=1 ),

In the sentence

ElementType.TYPE can be applied to the declaration of a class, an abtract class, an interface, an annotation interface, an enumeration, or a record declaration.

"an abtract class" should be an abstract class.

In the latest version of https://dev.java/learn/getting-started/ (archived as is at https://web.archive.org/web/20260714011832/https://dev.java/learn/getting-started/ ),

In the sentence,

The Java VM requires that the class you execute with it hase a main method at which to begin execution of your application.

"hase" should be "has". (Note that as of https://openjdk.org/jeps/512 simple programs can be written with a standalone "void main() {}" with no explicitly declared class.)

In the latest version of https://dev.java/learn/debugging/ (archived as is at https://web.archive.org/web/20260714060248/https://dev.java/learn/debugging/?nonce=1 ),

In the sentence,

This allows you to deicde when you want to debug.

"deicde" should be "decide".
In the sentence,

However, it can quickly get unmanagable in a more complicated program especally if you have multiple things to keep track of or a lot of loops.

"especally" should be "especially".

In the latest version of https://dev.java/learn/eclipse/ (archived as is at http://web.archive.org/web/20260714061649/https://dev.java/learn/eclipse/ ),

In the sentence,

Upon selecting a workspace, it will show a Welcome screen presenting you with mutliple options.

"mutliple" should be "multiple".

In the latest version of https://dev.java/learn/numbers-strings/numbers/ (archived as is at http://web.archive.org/web/20260714062520/https://dev.java/learn/numbers-strings/numbers/ ),

In the heading

Rouding a Value

"Rouding" should be "Rounding".

In the latest version of https://dev.java/learn/vscode-java/ (archived as is at https://web.archive.org/web/20260714011605/https://dev.java/learn/vscode-java/ )

In the sentence

You can invoke the launch configuration/debugger when you select Run main | Debug main code lense or from the Run and Debug activity panel.

"lense" should be "lens".

In the latest version of https://dev.java/learn/lambdas/first-lambdas/ (archived as is at http://web.archive.org/web/20260714075742/https://dev.java/learn/lambdas/first-lambdas/?nonce=1 ),

In the sentence,

So everytime you write a lambda,
you can call any method defined
on the interface this lamdba is implementing.

the 2nd time "lambda" is intended, it is spelled incorrectly.
That is on the 3rd line above "lamdba" should be "lambda" .

Thanks so much!

Thank you again for your report! A fix is on its way.

Thanks! That first example I sent is not fixed yet ("prinln" still needs to be updated to "println" as indicated in my last comment, and it is repeated in the list below along with the newly reported typos).

Here are some more typos I have found (not guaranteeing these are the only issues with those pages, but no reason not to fix these typos since they have been detected):

In the latest version of https://dev.java/learn/jvm/tool/security/keytool/ (archived as is at https://web.archive.org/web/20260715234313/https://dev.java/learn/jvm/tool/security/keytool/?nonce=2 ),

In the line

BC or BasicContraints

"BasicContraints" should be "BasicConstraints".
In the sentence

The CA authenticates the certificate requestor (usually offline) and returns a certificate or certificate chain to replace the existing certificate chain (initially a self-signed certificate) in the keystore.

"requestor" should be "requester".

In the latest version of https://dev.java/learn/debugging/ (archived as is at https://web.archive.org/web/20260715231111/https://dev.java/learn/debugging/) ,

in the sentence

However, it can quickly get unmanagable in a more complicated program especially if you have multiple things to keep track of or a lot of loops.

"unmanagable" should be "unmanageable".

In the latest version of https://dev.java/learn/jvm/jfr/intro/ (archived as is at https://web.archive.org/web/20260715230756/https://dev.java/learn/jvm/jfr/intro/ ),

In the sentence

This greatly lowers the barrier of entry for using JFR as extensive security reviews or product evaulations are not necessary.

"evaulations" should be "evaluations".
In the sentence

Users are able to configure how JFR collects events, and even define their own events for collecting additional data about thier applications.

"thier" should be "their".

In the latest version of https://dev.java/learn/jvm/tool/garbage-collection/intro/ (archived as is at https://web.archive.org/web/20260715231250/https://dev.java/learn/jvm/tool/garbage-collection/intro/ ),

in the heading

Memory Managment

"Managment" should "Management".

In the latest version of https://dev.java/learn/jvm/tool/garbage-collection/java-specifics/ (archived as is at https://web.archive.org/web/20260715235827/https://dev.java/learn/jvm/tool/garbage-collection/java-specifics/?nonce=4 ),

in the sentences

This in turn means that during a garbage collection, part, or all, of the JVM must be paused for a period while the garbage collector works to prevent errors from occuring as objects are checked for usage, deleted, and moved or copied.
[...]
Tools like JDK Flight Recorder (JFR) and Visual VM can be used to monitor the frequency and duration of pauses occuring from garbage collection.

"occuring" should be "occurring" (in two places above).

In the sentence

Though note that dependening on the garbage collector implementation, there might be additional sub-phases within each phase that are not covered here.

"dependening" should be "depending".
In the sentence

How to tune a garbage collector is outside the scope of this tutorial, but monitoring garbage collector behavior, and subseqently tuning it through JVM arguments, can be key way to improve the performance of an application.

"subseqently" should be "subsequently".

In the latest version of https://dev.java/learn/classes-objects/creating-objects/ (archived as is at https://web.archive.org/web/20260716001528/https://dev.java/learn/classes-objects/creating-objects/?nonce=5 )

in the sentence,

For example, the folllowing code is outside the code for the Rectangle class.

"folllowing" should be "following".

In the latest version of https://dev.java/learn/date-time/non-iso-conversion/ (archived as is at https://web.archive.org/web/20260716001550/https://dev.java/learn/date-time/non-iso-conversion/?nonce=5 )

in the sentence,

The ouput looks like this:

"ouput" should be "output".

In the latest version of https://dev.java/learn/jvm/jfr/getting-started/ (archived as is at https://web.archive.org/web/20260716001938/https://dev.java/learn/jvm/jfr/getting-started/?nonce=5 )

in the sentence

In inclusion to the the jcmd actions; JFR.start and JFR.dump already covered, jcmd provides three other adminstrator actions.

"adminstrator" should be "administrator".

In the latest version of https://dev.java/learn/refactoring-to-functional-style/convertingtostreams/ (archived as is at https://web.archive.org/web/20260716002322/https://dev.java/learn/refactoring-to-functional-style/convertingtostreams/?nonce=3 )

in the sentence

Here's an all too familiear imperative style code to accomplish that task:

"familiear" should be "familiar".

In the latest version of https://dev.java/learn/regex/patterns/ (archived as is at https://web.archive.org/web/20260716002952/https://dev.java/learn/regex/patterns/?nonce=3 )

In the sentence

As you can see, the string literal "dog" matches both occurences, regardless of case.

"occurences" should be "occurrences"

In the latest version of https://dev.java/learn/jvm/tool/garbage-collection/zgc-overview/ (archived as is at https://web.archive.org/web/20260716003010/https://dev.java/learn/jvm/tool/garbage-collection/zgc-overview/?nonce=6 )

In the sentence

ZGC will automatically set the number of concurrent threads it will use through internal GC hueristics, however this setting can be manually configured to [sentence is not finished within the article?]

"hueristics" should be "heuristics" AND the sentence ends incomplete (should be finished).

In the latest version of https://dev.java/learn/language-basics/arrays/ (archived as is https://web.archive.org/web/20260716003938/https://dev.java/learn/language-basics/arrays/?nonce=6 )

In the code example
```
var coffeesAsString = Arrays.toString(coffees);
IO.prinln(coffeesAsString);
```
"prinln" should be "println" (this was reported in my last comment above along with other errors in the same code box but the dev.java team did not fix this yet).

In the latest version of https://dev.java/learn/generics/type-erasure/ (archived as is https://web.archive.org/web/20260716004241/https://dev.java/learn/generics/type-erasure/?nonce=2 )

in the sentence

The following example, HeapPollutionExample uses the ArrayBuiler class:

"ArrayBuiler" should be "ArrayBuilder"

In the latest version of https://dev.java/learn/jvm/tool/troubleshooting/jcmd/ (archived as is at https://web.archive.org/web/20260715233521/https://dev.java/learn/jvm/tool/troubleshooting/jcmd/ ),

In the sentences

globalbuffercount: (Optional) Number of global buffers. This option is a legacy option: change the memorysize parameter to alter the number of global buffers. This value cannot be changed once JFR has been initalized. (STRING, default determined by the value for memorysize)

globalbuffersize: (Optional) Size of the global buffers, in bytes. This option is a legacy option: change the memorysize parameter to alter the size of the global buffers. This value cannot be changed once JFR has been initalized. (STRING, default determined by the value for memorysize)

"initalized" should be "initialized" (in two places).

Thanks so much!

Thank you again for your report! A fix is on its way.

Thanks!

In the latest version of https://dev.java/learn/jvm/tool/troubleshooting/jcmd/ (archived as is at https://web.archive.org/web/20260718025151/https://dev.java/learn/jvm/tool/troubleshooting/jcmd/ ),

In the sentence

On Windwows, the temporary directory is specified by the TMP environment variable.)

"Windwows" should be "Windows".
In the sentence

jmxremote.autodiscovery: (Optional) Sets com.sun.management.jmxremote.au todiscovery (STRING, no default value)

the space between "au" and "to" in "com.sun.management.jmxremote.au todiscovery" should be removed.

In the latest version of https://dev.java/learn/jvm/tool/security/keytool/ (archived as is at https://web.archive.org/web/20260717221310/https://dev.java/learn/jvm/tool/security/keytool/?nonce=1 ),

In the sentence

The CA authenticates you, the requestor (usually offline), and returns a certificate, signed by them, authenticating your public key.

"requestor" should be "requester". This same typo in a different sentence in this same page was previously reported to and fixed by the dev.java team, but it occurs again here.

In the latest version of https://dev.java/learn/security/intro/ (archived as is at https://web.archive.org/web/20260718025455/https://dev.java/learn/security/intro/ ),

In the code example

KeyPair keypair = generateRSAKKeyPair();

"RSAKKey" should be "RSAKey" (same as method declaration above it). The typo of RSAKKey was fixed by the dev.java team in some other positions but not here yet.

In the latest version of https://dev.java/learn/reflection/enums/ (archived as is at https://web.archive.org/web/20260718063324/https://dev.java/learn/reflection/enums/ ),

In the code example output

constuctor[0]: private org.devjava.Days(java.lang.String,int,java.lang.String)

"constuctor" should be "constructor" , and the preceding code example needs to have a print statement added to generate this output.

In the latest version of https://dev.java/learn/language-basics/arrays/ (archived as is at https://web.archive.org/web/20260718063757/https://dev.java/learn/language-basics/arrays/?nonce=12 ),

In the sentence

Affogato Americano Cappuccino Corretto Cortado Doppio Espresso Frappucino Freddo Lungo Macchiato Marocchino Ristretto

"Frappucino" should be "Frappuccino".

Thanks!

Thank you again for your report! A fix is on its way.

Thanks so much!

In the latest version of https://dev.java/learn/jvm/tool/garbage-collection/java-specifics/ (archived as is at https://web.archive.org/web/20260718224416/https://dev.java/learn/jvm/tool/garbage-collection/java-specifics/?nonce=1 ),

In the sentence

The final phase of a garbage collection is the compaction phase. Live objects in the eden region or an occupied survivor region are moved and/or copied to an empty survivor region. If an object in a survivor region has gained enough tenureship, it is moved or copied to an old region.

"tenureship" (not a valid word) should be "tenure".

In the latest version of https://dev.java/learn/jvm/tools/core/javadoc/ (archived as is at https://web.archive.org/web/20260718225352/https://dev.java/learn/jvm/tools/core/javadoc/?no_cache=true )

In the sentence

Thehtml-code value is placed to the right of the lower navigation bar.

there should be a space between "The" and "html-code".

In the latest version of https://dev.java/learn/jvm/tools/core/java/ (archived as is at https://web.archive.org/web/20260718230428/https://dev.java/learn/jvm/tools/core/java/?nonce=3 )

In the sentence

Setting this option is equivalent to running the jstack -l command or thejcmd pid Thread.print -l command, where pid is the current Java process identifier.

it seems "thejcmd" should be "the jcmd". Probably the commands should be styled to set them apart from the enclosing sentence as well.

Thanks!

Thank you again for your report! A fix is on its way.

Can you confirm those changes were deployed? I don't see that any updates for the items reported in my last comment were deployed yet. Thanks so much!

Sorry for the delay. It should be live in a few mn now.

Thanks, I can confirm the typos reported above have been fixed on the live site.

Here are some additional typos that were uncovered after the above were reported (waiting for those to be ack'd/fixed first).

In the latest version of https://dev.java/learn/javafx/core/all/ (archived with a fresh snapshot as is at https://web.archive.org/web/20260724231031/https://dev.java/learn/javafx/core/all/?nonce=1 )

In the sentence

Afterall, JavaFX is implemented with Java APIs and can certainly take advantage of new features as they become available.

"Afterall" should be "After all".

In the latest version of https://dev.java/learn/jvm/tool/troubleshooting/jcmd/ (archived with a fresh snapshot as is at https://web.archive.org/web/20260724231105/https://dev.java/learn/jvm/tool/troubleshooting/jcmd/?nonce=2 )

In the line

jmxremote.access.file: (Optional) Sets com.sun.management.jmxremote.acce ss.file (STRING, no default value)
```
 "acce ss" should be "access".
```

In the latest version of https://dev.java/learn/jvm/tools/core/jmod/ (archived as is at https://web.archive.org/web/20260724234347/https://dev.java/learn/jvm/tools/core/jmod/?nonce=1 )

In the line

You may comment out lines by prefixinga hash symbol (#) to the beginning of the line.

"prefixinga" should be "prefixing a".

Thanks very much!

Thank you again for your report! A fix is on its way.

Thanks! I can confirm the items reported above were fixed.

(Note that on one of the pages which has a typo reported above, https://dev.java/learn/javafx/core/all/ , the uncapitalized "t" in "Putting it All together" was also reported by me earlier separately at #258 (comment) so I will not block this typo focused ticket on that.)

Here are some additional typos I have found during my ongoing review:

On the page https://dev.java/learn/jvm/tool/security/ktabd/ (archived as is at https://web.archive.org/web/20260729010413/https://dev.java/learn/jvm/tool/security/ktabd/ )

In the sentence

etype should be specified as the numberic value etype defined in RFC 3961, section 8.

"numberic" is not a valid word; this was probably intended to be "numeric".

On the page https://dev.java/learn/api/streams/gatherers/ (archived as is at https://web.archive.org/web/20260729005633/https://dev.java/learn/api/streams/gatherers/ )

In the sentence,

Everytime you consume an element, you need to check if it has already been seen or not. And in that case, you should not push it to the downstream.

"Everytime" should be "Every time".

On the page https://dev.java/learn/api/streams/creating/ (archived as is at https://web.archive.org/web/20260729010137/https://dev.java/learn/api/streams/creating/ )

In the sentence

Everytime a new element is needed, this supplier is called.

"Everytime" should be "Every time".

On the page https://dev.java/learn/jvm/tool/troubleshooting/jdb/ (archived as is at https://web.archive.org/web/20260729011755/https://dev.java/learn/jvm/tool/troubleshooting/jdb/ )

In the sentence

The following options are forwarded to the debuggee process:

it seems that "debuggee" in this case should probably be "debugger" (compare to early versions of this same content hosted at Oracle, e.g. https://docs.oracle.com/javase/8/docs/technotes/tools/windows/jdb.html ; though the same seeming typo shows on more recent Oracle-side pages as well https://docs.oracle.com/en/java/javase/23/docs/specs/man/jdb.html ).

Thanks very much!

Thank you again for your report! A fix is on its way.

Excellent. I can confirm I see that the items reported above have been fixed by the dev.java team.

Remaining:
I should have reported that in one of the pages above the dev.java team had "everytime" twice (I reported one instance), so that it still needs to be changed to "every time" in one place:

On https://dev.java/learn/api/streams/gatherers/ (archived as is at https://web.archive.org/web/20260724223402/https://dev.java/learn/api/streams/gatherers/?nonce=2 )

In the sentence

So everytime the Stream API runs a gatherer in a thread, it creates a new instance of this mutable state for this gatherer to work with.

"everytime" should be "every time".

Thanks!

Note there is an analogous typo roll-up ticket for inside.java that I opened at java/devrel#54 for ease of reference between the two. Thanks!

Thanks for resolving the typos reported above. Here are some additional remaining typos from across dev.java:

In the latest version of https://dev.java/learn/lambdas/first-lambdas/ (archived as is at https://web.archive.org/web/20260806131649/https://dev.java/learn/lambdas/first-lambdas/ )

In the sentence

So everytime you write a lambda, you can call any method defined on the interface this lambda is implementing.

"everytime" should be "every time".
In the sentence

This process of accessing variable is called capturing: lambdas cannot capture variables, they can only capture values.

"accessing variable" should be "accessing a variable".

In the latest version of https://dev.java/learn/records/ (archived as is at https://web.archive.org/web/20260806131803/https://dev.java/learn/records/?nonce=20 )

In the sentence

It reduces the risk of bugs because everytime you modify the components of a record, the compiler automatically updates the equals() and hashCode() methods for you.

"everytime" should be "every time".

In the latest version of https://dev.java/learn/lambdas/combining-chaining-composing/ (archived as is at https://web.archive.org/web/20260806182904/https://dev.java/learn/lambdas/combining-chaining-composing/?nonce=20 )

In the sentence

can chain them by calling [f1.andThen(f2).

the extra "[" should be removed.

Thanks so much!

Navigation Menu

Repository navigation

Typos in various articles (multi-article typo only ticket) #263

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Typos in various articles (multi-article typo only ticket) #263

Description

Activity

JosePaumard commented on Jul 15, 2026

willy-b commented on Jul 16, 2026

JosePaumard commented on Jul 16, 2026

willy-b commented on Jul 18, 2026

JosePaumard commented on Jul 18, 2026

willy-b commented on Jul 19, 2026

JosePaumard commented on Jul 20, 2026

willy-b commented on Jul 21, 2026

JosePaumard commented on Jul 24, 2026

willy-b commented on Jul 24, 2026

JosePaumard commented on Jul 26, 2026

willy-b commented on Jul 30, 2026

JosePaumard commented on Jul 31, 2026

willy-b commented on Aug 1, 2026

willy-b commented on Aug 4, 2026

willy-b commented on Aug 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions