What happened?

Hello Java DevRel team!

Thanks for all the excellent content!

I am primarily a reader of dev.java but after finding some typos on that site, I decided to take a look at inside.java (linked from dev.java). I wanted to report some apparent typos I found on inside.java posts (list below). Feel free to leave the issue open after resolving the typos and I can review to confirm they are fixed and add any additional ones I may find during the intervening time.

---

In the latest version of https://inside.java/2026/03/02/jdk-26-rn-ops/ (archived as is at https://web.archive.org/web/20260722010205/https://inside.java/2026/03/02/jdk-26-rn-ops/?nonce=1 ),

• In the sentence

  Testing has shown that these changes have improved throughput by 5-15% percent, with applications that do heavy modification to object-reference fields seeing the most benefit. Additionally this new design is more efficent that the previous auxillry data structure, which resulted in a slight descrease in pause times.

  "descrease" should be "decrease", "efficent" should be "efficient", "auxillry" should be "auxiliary".

• In the sentence

  Protocal Requires for JMXServiceURL

  "Protocal Requires" should be "Protocol Requirements".

• In the sentence

  This has been updated to not select jmxmp and instead print out the follow and more clear message:

  "the follow and more clear" should be "the following, more clear"

• In the output

  "Misssing protocol name at java.management/"

  "Misssing" should be "Missing".

• In the sentence

  Lastly the second card table can in some cases slightly reduce memory overhead; each card table requiring about 2MB of native meory per 1GB of heap capacity.

  "meory" should be "memory".

---

In the latest version of https://inside.java/2025/04/10/newscast-89/ (archived as is at https://web.archive.org/web/20260722003915/https://inside.java/2025/04/10/newscast-89/?nonce=1 ),

• In the sentence

  An explanation for why not to use unit tests for AOT training runs on JDK 24, a garbage collection primer and comparison,
  two tips on how to analyze your Maven build, the announcement that final will eventually mean really final and how to simulate that today,
  a detailed look at how to build an advanced retrieval augmenter for quering AI models, and last but not least, the roadmap for value types and null restriction.

  "quering" should be "querying".

---

In the latest version of https://inside.java/2022/09/20/sip066/ (archived as is at https://web.archive.org/web/20260722004016/https://inside.java/2022/09/20/sip066/?nonce=1 ),

• In the sentence

  The Foreign Function and Memory API allows Java applications to interact with code and data outside the JVM,
  more safely than what is provided by the Java Native Interace (JNI).

  "Interace" should be "Interface".

---

In the latest version of https://inside.java/2021/04/30/failed-writing-core-dump/ (archived as is at https://web.archive.org/web/20260722004104/https://inside.java/2021/04/30/failed-writing-core-dump/?nonce=1 ),

• In the column label

  JDK 9+ argumnet

  "argumnet" should be "argument".

---

In the latest version of https://inside.java/2020/06/25/compact-forwarding/ (archived as is at https://web.archive.org/web/20260722004153/https://inside.java/2020/06/25/compact-forwarding/?nonce=2 ),

• In the sentence

  ZGC moves objects around, to combat memory fragmenation, without stopping the application.

  "fragmenation" should be "fragmentation".

• In the sentence

  As part of my thesis work, we propose a new design for forwarding tables that maps several sparesly populated pages (i.e., with few live objects) onto a single new page in a way that allows the to-address to be calculated using the from-address and liveness information.

  "sparesly" should be "sparsely".

• In the sentence

  But I'm fairly hopeful that decrease in memory footprint and predictable overhead outweighs the increase in execution time, as incidated by the measurements.

  "incidated" should be "indicated".

---

In the latest version of https://inside.java/2023/10/05/newscast-56/ (archived as is at https://web.archive.org/web/20260722004515/https://inside.java/2023/10/05/newscast-56/?nonce=1 ),

• In the sentence

  The new class-file API that Brian Goetz presented at JVMLS in august 2023 will improve that situation greatly by shipping an always up-to-date bytecode anlysis and manipulation API with the JDK.

  "anlysis" should be "analysis".

---

In the latest version of https://inside.java/2020/12/21/podcast-010/ (archived as is at https://web.archive.org/web/20260722004714/https://inside.java/2020/12/21/podcast-010/?nonce=1 ),

• In the sentence

  Make sure to also listen to Episode 9 where Panama was introduced, and the Foreign Memroy Access API was discussed in details.

"Memroy" should be "memory".

---

In the latest version of https://inside.java/2021/10/21/sip24/ (archived as is at https://web.archive.org/web/20260722005033/https://inside.java/2021/10/21/sip24/?nonce=1 ),

• In the sentence

  However when deserializing data that violates that requirment like in the example below:

  "requirment" should be "requirement".

---

In the latest version of https://inside.java/2025/02/06/quality-heads-up/ (archived as is at https://web.archive.org/web/20260722005143/https://inside.java/2025/02/06/quality-heads-up/?nonce=2 ),

• In the sentence

  Any historical connection with the -UseCompresseedOops have long since been removed, and the net result of -UseCompressedClassPointers is simply increased memory overhead.

  "UseCompresseedOops" should be "UseCompressedOops".

---

In the latest version of https://inside.java/2019/10/02/strippingdebug-jlink/ (archived as is at https://web.archive.org/web/20260722020442/https://inside.java/2019/10/02/strippingdebug-jlink/?nonce=1 ),

• In the sentence

  jlink also comes with some additonal plugins, some of which
  will help to additionaly reduce the size of the produced custom runtime
  image — namely the compress and the strip-debug plugins.

  "additonal" should be "additional"

  "additionaly" should be "additionally".

---

In the latest version of https://inside.java/2024/01/16/wrapup-java-lang-features/ (archived as is at https://web.archive.org/web/20260722005620/https://inside.java/2024/01/16/wrapup-java-lang-features/?nonce=3 ),

• In the sentence

  The IDE generated project contains a starter class Wrappup.java in the package org.ammbra.advent.

  "Wrappup.java" should be "Wrapup.java" to match the code example provided beneath that sentence.

---

In the latest version of https://inside.java/2021/04/06/record-serialization-in-practise/ (archived as is at https://web.archive.org/web/20260722005722/https://inside.java/2021/04/06/record-serialization-in-practise/?nonce=1 ),

• In the sentence

  Looking at the implementation in more detail, an important aspect is JDK version compatability.

  "compatability" should be "compatibility".

• In the sentence

  We therefore embarked on an effort to help exisiting frameworks to support records adequately.

  "exisiting" should be "existing".

---

In the latest version of https://inside.java/2021/03/08/podcast-014/ (archived as is at https://web.archive.org/web/20260722005819/https://inside.java/2021/03/08/podcast-014/?nonce=1 ),

• In the sentence

  This was a good occasion for David to discuss Records, and more specifically Records serialisa... Records serialization with Julia Boes and Chris Hegarty.

  "Records serialisa... Records serialization" should be "Records serialization".

---

In the latest version of https://inside.java/2022/04/14/sip47/ (archived as is at https://web.archive.org/web/20260722005914/https://inside.java/2022/04/14/sip47/?nonce=2 ),

• In the sentence

  The Constant Field Values page displays all constant fields and their values, alphabatized by package, class, and then by field name.

  "alphabatized" should be "alphabetized" .

---

In the latest version of https://inside.java/2022/11/22/heads-up/ (archived as is at https://web.archive.org/web/20260722005956/https://inside.java/2022/11/22/heads-up/?nonce=1 ),

• In the sentence

  Before JDK 20, some of the parsing/validation performed by the JDK built-in URLStreamHander implementations were delayed until URL::openConnection or URLConnection::connect was called.

  "URLStreamHander" should be "URLStreamHandler".

---

In the latest version of https://inside.java/2021/02/12/deciphering-the-stacktrace/ (archived as is at https://web.archive.org/web/20260722010114/https://inside.java/2021/02/12/deciphering-the-stacktrace/?nonce=2 ),

• In the sentence

  Native code genereted by the JVM

  "genereted" should be "generated".

---

In the latest version of https://inside.java/2023/04/24/sip075/ (archived as is at https://web.archive.org/web/20260722010401/https://inside.java/2023/04/24/sip075/?nonce=1 ),

• In the sentence

  SecurirtyProviderService

  "Securirty" should be "Security".

---

In the latest version of https://inside.java/2023/10/15/g1/ (archived as is at https://web.archive.org/web/20260722010939/https://inside.java/2023/10/15/g1/ ),

• In the sentence

  Stack Walker - G1: Java's Default Garabge Collector

  "Garabge" should be "Garbage".

---

In the latest version of https://inside.java/2026/03/04/jdk-26-http-client/ (archived as is at https://web.archive.org/web/20260722011030/https://inside.java/2026/03/04/jdk-26-http-client/?nonce=2 ),

• In the sentence

  If it's likely the service you are connecting to does not support HTTP/3, then a pessimistic approach could be taken, and send a HTTP/1.1 or HTTP/2 request first, and only switching to HTTP/3 if the serivce says its available.

  "serivce" should be "service".

• In the sentence

  Sending requests in serial, like in the above example, can increase latency, espeically when a fallback is likely.

  "espeically" should be "especially".

---

In the latest version of https://inside.java/2025/06/29/javaone-leyden-aot/ (archived as is at https://web.archive.org/web/20260722011240/https://inside.java/2025/06/29/javaone-leyden-aot/?nonce=2 ),

• In the sentence

  JEP 483: “Ahead-of-Time Class Loading & Linking" in JDK 24 is the first instalment of this effort with more to follow. Join us as we explore how Leyden shifts work ahead of time based on speculating that future executions will be similar to previous executions of your program.

  "instalment" should be "installment".

---

In the latest version of https://inside.java/2023/05/08/quality-heads-up/ (archived as is at https://web.archive.org/web/20260722011430/https://inside.java/2023/05/08/quality-heads-up/?nonce=1 ),

• In the sentence

  This change may impact code that does a lookup of network interfaces with the NetworkInterace.getByName(String name) method.

  "Interace" should be "Interface".

---

In the latest version of https://inside.java/2021/09/10/what-are-modules-about/ (archived as is at https://web.archive.org/web/20260722011518/https://inside.java/2021/09/10/what-are-modules-about/?nonce=2 ),

• In the sentence

  This code — that's similar to all authorisation code — assumes that the sensitive operation, getUserData, is only ever called by safelyRetrieveUserData after an appropritate credentials check.

  "appropritate" should be "appropriate".

---

In the latest version of https://inside.java/2021/12/06/working-with-the-simple-web-server/ (archived as is at https://web.archive.org/web/20260722011936/https://inside.java/2021/12/06/working-with-the-simple-web-server/?nonce=1 ),

• In the sentence,

  For example, the command jwebserver serves the files of the current working directory. While this is suitable for certain uses cases (e.g. sharing and browsing files across the network), it can be a hinderance for others.

  "hinderance" should be "hindrance".

---

In the latest version of https://inside.java/2025/10/17/new-in-jdk-25-2-mins/ (archived as is at https://web.archive.org/web/20260722012101/https://inside.java/2025/10/17/new-in-jdk-25-2-mins/?nonce=1 ),

• In the sentence

  A StableValue can only be set once, put provides more fleixiblity than what the final keyword allows, which requires a variable to be set at either class or instance initialization.

  "fleixiblity" should be "flexibility".

---

In the latest version of https://inside.java/2025/10/27/try-jep-401-value-classes/ (archived as is at https://web.archive.org/web/20260722012231/https://inside.java/2025/10/27/try-jep-401-value-classes/?nonce=1 ),

• In the sentence

  Users are encouraged to review the feature doocumentation to get a better sense of what kind of optimizations are possible, and use profiling tools like JDK Mission Control and JMH to see how value objects affect their program’s performance.

  "doocumentation" should be "documentation".

---

In the latest version of https://inside.java/2025/08/27/thesis-gc-agnostic-load-barriers/ (archived as is at https://web.archive.org/web/20260722012421/https://inside.java/2025/08/27/thesis-gc-agnostic-load-barriers/?nonce=2 ),

• In the sentence

  Conesquently, compiled code using one GC cannot be used with another GC.

  "Conesquently" should be "Consequently".

---

In the latest version of https://inside.java/2022/11/29/quality-heads-up/ (archived as is at https://web.archive.org/web/20260722012520/https://inside.java/2022/11/29/quality-heads-up/?nonce=2 ),

• In the sentences

  Heuristics rewriten to deal with a problematic case where Generational ZGC spent too much focus on doing young generation collection when it's more beneficial to spend resources to collect the old generation.
  [...]
  GC logging rewriten to easier see what log lines belong to what collection / generation, plus many additional changes that should make it easier to read and understand GC logs.

  "rewriten" should be "rewritten" in two places.

---

In the latest version of https://inside.java/2021/10/04/the-default-charset-jep400/ (archived as is at https://web.archive.org/web/20260722012617/https://inside.java/2021/10/04/the-default-charset-jep400/?nonce=2 ),

• In the sentences

  This is not longer ncessary!

  "not long ncessary" should be "no longer necessary".

---

In the latest version of https://inside.java/2022/03/31/pattern-matching-elegance/ (archived as is at https://web.archive.org/web/20260722012732/https://inside.java/2022/03/31/pattern-matching-elegance/?nonce=3 ),

• In the sentence

  Presented by Venkat Subramaniam - Founder, Agile Develper, Inc.

  "Develper" should be "Developer".

---

In the latest version of https://inside.java/2025/03/27/newscast-88/ (archived as is at https://web.archive.org/web/20260722012824/https://inside.java/2025/03/27/newscast-88/?nonce=4 ),

• In the sentence

  This allows for lazy initialization that improves performance through laziness as well as better JIT opimizations.

  "opimizations" should be "optimizations".

---

In the latest version of https://inside.java/2024/07/16/build-oci-instance-with-java-concepts/ (archived as is at https://web.archive.org/web/20260722012919/https://inside.java/2024/07/16/build-oci-instance-with-java-concepts/?nonce=2 ),

• In the sentence

  And you should see somethig like

  "somethig" should be "something".

---

In the latest version of https://inside.java/2026/02/26/podcast-048/ (archived as is at https://web.archive.org/web/20260722013012/https://inside.java/2026/02/26/podcast-048/?nonce=2 ),

• In the sentence

  They start by briefly retracing its introduction in Java 11 and its support for HTTP/2 before diving deeper into HTTP/3 to learn about the motivation, technical underpinnings like the QUIC protocol, and challengs for its adoption before discussing its integration into Java 26.

  "challengs" should be "challenges".

---

In the latest version of https://inside.java/2023/04/03/hotspot-throughput-thesis/ (archived as is at https://web.archive.org/web/20260722004902/https://inside.java/2023/04/03/hotspot-throughput-thesis/?nonce=1 ),

• In the sentence

  M. Blackburn et al., “The DaCapo benchmarks: Java benchmarking development and analysis,” in OOPSLA ’06: Proceedings of the 21st annual ACM SIGPLAN conference on Object-Oriented Programing, Systems, Languages, and Applications.

  "Programing" should be "Programming".

• In the sentence

  This means that SAB does not cause any obvious throughput limitation, but only accives a statistically significant throughput increase for some specific benchmarks.

  "accives" should be "achieves".

• In the sentence

  Futhurmore, the other 17 / 21 benchmarks showed no significant regressions.

  "Futhurmore" should be "Furthermore".

• In the sentence

  My name is Filip Wilén and I wrote my master's thesis at Oracle during autum 2022.

  "autum" should be "autumn".

---

In the latest version of https://inside.java/2023/11/13/sip088/ (archived as is at https://web.archive.org/web/20260722013308/https://inside.java/2023/11/13/sip088/?nonce=2 ),

• In the sentence

  Sealed Hierachies

  "Hierachies" should be "Hierarchies".

---

In the latest version of https://inside.java/2026/02/20/podcast-046/ (archived as is at https://web.archive.org/web/20260722013401/https://inside.java/2026/02/20/podcast-046/?nonce=2 ),

• In the link text

  Valhalla early acces build

  "acces" should be "access".

---

In the latest version of https://inside.java/2022/10/18/generationalzgc-ea/ (archived as is at https://web.archive.org/web/20260722013501/https://inside.java/2022/10/18/generationalzgc-ea/?nonce=2 ),

• In the sentence

  After a lot of hard work on Generational ZGC, the first Early Access builds have been pubished at jdk.java.net/genzgc and are available for testing.
  Proper feedback should be reported to the zgc-dev mailing list.

  "pubished" should be "published".

---

In the latest version of https://inside.java/2021/09/16/finalizing-the-foreign-apis/ (archived as is at https://web.archive.org/web/20260722013931/https://inside.java/2021/09/16/finalizing-the-foreign-apis/?nonce=2 ),

• In the sentence

  This means that the above linkage request can be expressed more succintly as follows:

  "succintly" should be "succinctly".

---

In the latest version of https://inside.java/2020/12/03/crash-outside-the-jvm/ (archived as is at https://web.archive.org/web/20260722014426/https://inside.java/2020/12/03/crash-outside-the-jvm/?nonce=1 ),

• In the sentence

  To find cues, you want to look in the generated hs_err file. Below is an example of a crash that occured when running Minecraft.

  "occured" should be "occurred".

---

In the latest version of https://inside.java/2022/05/27/testing-clean-cleaner-cleanup/ (archived as is at https://web.archive.org/web/20260722014929/https://inside.java/2022/05/27/testing-clean-cleaner-cleanup/?nonce=1 ),

• In the sentence

  The SensitiveData example code and the SensistiveDataTest test code are available in a SensitiveData Gist.

  "Sensistive" should be "Sensitive".

---

In the latest version of https://inside.java/2025/07/29/just-be-lazy/ (archived as is at https://web.archive.org/web/20260722015021/https://inside.java/2025/07/29/just-be-lazy/?nonce=3 ),

• In the line of code

  private static final OrderControler ORDER_CONTROLLER = OrderControllerImpl.create();

"OrderControler" should be "OrderController".

---

In the latest version of https://inside.java/2025/09/21/jvmls-java-additional-numeric-types/ (archived as is at https://web.archive.org/web/20260722015123/https://inside.java/2025/09/21/jvmls-java-additional-numeric-types/?nonce=2 ),

• In the sentence

  This talk discusses the aspects needed to provide full support for
  new numeric types in the Java platform and presents trade-offs on
  different paths to provide that support

  "ff" (special character) in two places should be "ff".

---

In the latest version of https://inside.java/u/ShaunSmith/ (archived as is at https://web.archive.org/web/20260722015214/https://inside.java/u/ShaunSmith/?nonce=1),

• In the sentence

  Senior Director of Product Managment - Oracle Labs @ GraalVM

  "Managment" should be "Management".

---

In the latest version of https://inside.java/2021/11/30/on-parallelism-and-concurrency/ (archived as is at https://web.archive.org/web/20260722020448/https://inside.java/2021/11/30/on-parallelism-and-concurrency/?nonce=1 ),

• In the sentence

  In this case, there might be a fundamental difficulty in understsanding
  the problem, and it's not a new one: the confusion between concurrency
  and parallelism.

  "understsanding" should be "understanding".

---

(No AI or LLM used, just my own typo-spider program, a plain Java program using only Java APIs (no HTML parser used), which pulls text from webpages, preprocessing a little to split camel case variables, and passes words to the open-source local spell checker (NO AI) hunspell (plain dictionary).)

Hopefully reporting these typos is useful to the team.

Thanks very much!

What OS are you seeing the problem on?

Linux

What browsers are you seeing the problem on?

Firefox

Contact Details (optional)

adde.animulis@gmail.com