misc: fix typos (#14990)

Thank you.

Author: jbampton

build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/java/TestsAndRandomizationPlugin.java

@@ -483,7 +483,7 @@ public void apply(Project project) {
 
               // Disable automatic test class detection, rely on class names only. This is needed
               // for testing
-              // against JDKs where the bytecode is unparseable by Gradle, for example.
+              // against JDKs where the bytecode is unparsable by Gradle, for example.
               // We require all tests to start with Test*, this simplifies include patterns greatly.
               task.setScanForTestClasses(false);
               task.include("**/Test*.class");

build-tools/missing-doclet/src/java/org/apache/lucene/missingdoclet/MissingDoclet.java

@@ -278,7 +278,7 @@ && level(element) >= METHOD) {
    * elements. UweSays: It should not happen but it happens!
    */
   private boolean isSyntheticMethod(Element element) {
-    // exclude all not explicitely declared methods
+    // exclude all not explicitly declared methods
     if (elementUtils.getOrigin(element) != Origin.EXPLICIT) {
       return true;
     }

dev-docs/file-formats.md

@@ -78,7 +78,7 @@ field.
 ## Add codec headers and footers to all files
 
 Use `CodecUtil` to add headers and footers to all files of the index. This
-helps make sure that we are opening the right file and differenciate Lucene
+helps make sure that we are opening the right file and differentiate Lucene
 bugs from file corruptions.
 
 ## Validate checksums of the metadata file when opening a segment

dev-tools/scripts/pyproject.toml

@@ -94,7 +94,7 @@ ignore = [
   "PLW0603", # using global statement to update variable is discouraged
   "PLW2901", # loop variable overwritten by assignment target
   "PTH104",  # os.rename should be replaced by Path.rename
-  "PTH107",  # os.remove shoudl be replaced by Path.unlink
+  "PTH107",  # os.remove should be replaced by Path.unlink
   "PTH109",  # os.getcwd should be replaced by Path.cwd
   "PTH110",  # os.path.exists should be replaced by Path.exists
   "PTH111",  # os.path.expanduser should be replaced by Path.expanduser
@@ -126,7 +126,7 @@ ignore = [
   "S506",    # probable use of unsafe yaml loader, consider yaml.safe_load
   "S602",    # subprocess call with shell=True identified, security issue
   "S603",    # subprocess call: check for execution of untrusted input
-  "S605",    # starting a process wtih a shell, seems safe, but may be changed in future
+  "S605",    # starting a process with a shell, seems safe, but may be changed in future
   "S607",    # starting a process with a partial executable path
   "S701",    # consider using jinja autoescape=True to mitigate XSS
   "SIM102",  # use single if statement instead of nested if statement

dev-tools/scripts/releaseWizard.yaml

@@ -25,7 +25,7 @@
 #
 # Templates may be included in any text by starting a line with this syntax:
 # (( template=my_template_name ))
-# Templates may contain other templates for easy re-use of snippets
+# Templates may contain other templates for easy reuse of snippets
 # And of course all Jinja2 syntax for inclusion of variables etc is supported.
 # See http://jinja.pocoo.org/docs/2.10/templates/ for details
 # To add new global variables or functions/filters, edit releaseWizard.py
@@ -143,12 +143,12 @@ templates:
 #   description: Longer description that will appear in sub-menu
 #   depends: ['group1_id', 'group2_id'] # Explicit dependencies for groups
 #   is_in_rc_loop: Tells that a group is thrown away on RC re-psin (default=False)
-#   todos:    # Array of !Todo objects beloning to the group
+#   todos:    # Array of !Todo objects belonging to the group
 #     !Todo
 #     id: todo_id
 #     title: Short title that will appear in menu and elsewhere
 #     description: |
-#         The main description being printed when selecing the todo item. Here
+#         The main description being printed when selecting the todo item. Here
 #         you should introduce the task in more detail. You can use {{ jinja_var }} to
 #         reference variables. See `releaseWizard.py` for list of global vars supported.
 #         You can reference state saved from earlier TODO items using syntax
@@ -202,7 +202,7 @@ groups:
   title: Prerequisites
   description: |
     Releasing software requires thorough understanding of the process and careful execution,
-    as it is easy to make mistakes. It also requires an environtment and tools such as gpg
+    as it is easy to make mistakes. It also requires an environment and tools such as gpg
     correctly setup. This section makes sure you're in good shape for the job!
   todos:
   - !Todo
@@ -1030,7 +1030,7 @@ groups:
       Fortunately the only thing you need to change is a few variables in `pelicanconf.py`.
       If you release a current latest release, change the `LUCENE_LATEST_RELEASE` and `LUCENE_LATEST_RELEASE_DATE`
       variables.
-      If you relese a bugfix release for previous version, then change the `LUCENE_PREVIOUS_MAJOR_RELEASE` variable.
+      If you release a bugfix release for previous version, then change the `LUCENE_PREVIOUS_MAJOR_RELEASE` variable.
     commands: !Commands
       root_folder: '{{ git_website_folder }}'
       commands_text: Edit pelicanconf.py to update version numbers
@@ -1256,7 +1256,7 @@ groups:
     For feature releases, your announcement should describe the main features included
     in the release. *Send the announce as Plain-text email, not HTML.*
 
-    This step will generate email templates based on the news files you edited earler for the website.
+    This step will generate email templates based on the news files you edited earlier for the website.
     Do any last-minute necessary edits to the text as you copy it over to the email.
   todos:
   - !Todo
@@ -1527,7 +1527,7 @@ groups:
         cmd: git commit -m "Add back-compat indices for {{ release_version }}"  && git push
         logfile: commit.log
     post_description: |
-      When doing a major version release, eg. 8.0.0, you might also need to reenable some
+      When doing a major version release, eg. 8.0.0, you might also need to re-enable some
       backward compatibility tests for corner cases. To find them, run grep -r assume
       lucene/backward-codecs/, which should find tests that have been disabled on main
       because there was no released Lucene version to test against.

help/regeneration.txt

@@ -20,7 +20,7 @@ Checksum validation errors
 --------------------------
 
 LUCENE-9868 introduced a system of storing (and validating) checksums of
-generated files so that they are not accidentally modified. This checkums
+generated files so that they are not accidentally modified. This checksums
 system will fail the build with a message similar to this one:
 
 Execution failed for task ':lucene:core:generateStandardTokenizerChecksumCheck'.

lucene/analysis/stempel/src/test/org/egothor/stemmer/TestStemmer.java

@@ -120,7 +120,7 @@ public void testMultiTrie2() {
     String[] keys = {"a", "ba", "bb", "c"};
     /*
      * short vals won't work, see line 155 for example
-     * the IOOBE is caught (wierd), but shouldnt affect patch cmds?
+     * the IOOBE is caught (weird), but shouldn't affect patch cmds?
      */
     String[] vals = {"1111", "2222", "2223", "4444"};
 
@@ -137,7 +137,7 @@ public void testMultiTrie2Backwards() {
     String[] keys = {"a", "ba", "bb", "c"};
     /*
      * short vals won't work, see line 155 for example
-     * the IOOBE is caught (wierd), but shouldnt affect patch cmds?
+     * the IOOBE is caught (weird), but shouldn't affect patch cmds?
      */
     String[] vals = {"1111", "2222", "2223", "4444"};