From 94e1b11e7df1af1cfecc934fc2bb119ef3fec448 Mon Sep 17 00:00:00 2001 From: by1361092 Date: Thu, 30 Jul 2026 05:43:08 +0000 Subject: [PATCH] 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package Reviewed-by: liach, amitkumar --- .../classes/java/lang/classfile/attribute/package-info.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/java.base/share/classes/java/lang/classfile/attribute/package-info.java b/src/java.base/share/classes/java/lang/classfile/attribute/package-info.java index 43bf1984a00..2525b8c6bc3 100644 --- a/src/java.base/share/classes/java/lang/classfile/attribute/package-info.java +++ b/src/java.base/share/classes/java/lang/classfile/attribute/package-info.java @@ -61,7 +61,7 @@ *

Writing Attributes

* Most attributes implement at least one of {@link ClassElement}, {@link FieldElement}, {@link MethodElement}, or * {@link CodeElement}, so they can be sent to the respective {@link ClassFileBuilder} to be written as part of those - * structure. Attributes define if they can {@linkplain AttributeMapper#allowMultiple() appear multiple times} in one + * structures. Attributes define if they can {@linkplain AttributeMapper#allowMultiple() appear multiple times} in one * structure; if they cannot, the last attribute instance supplied to the builder is the one written to the final * structure. Some attributes, such as {@link BootstrapMethodsAttribute}, implement none of those interfaces. They are * created through other means, specified in the modeling interface for each of the attributes. Attributes for a {@link @@ -69,7 +69,7 @@ *

* The attribute factories generally have two sets of factory methods: one that accepts symbolic information * representing the uses, and another that accepts constant pool entries. Most of time, the symbolic factories are - * sufficent, but the constant pool entry ones can be used for fine-grained control over {@code class} file generation; + * sufficient, but the constant pool entry ones can be used for fine-grained control over {@code class} file generation; * see "{@linkplain java.lang.classfile.constantpool##writing Writing the constant pool entries}" for more details. *

* Many attributes can be bulk-copied if the data it depends on does not change; this information is exposed in {@link