Fix formatting of releng.md java section

RELENG.md

@@ -54,7 +54,7 @@ The builds themselves and their unit tests are in the (Y Builds)[JenkinsJobs/YBu
 When the JDT team is ready they will raise an issue to create new Y and P builds and supply the name of the new branch, usually BETA_JAVA##.
 
 **Things to Do:**
-  1. Create a new maven profile for the java release by creating a patch folder under (eclipse.platform.releng.tychoeclipsebuilder)[eclipse.platform.releng.tychoeclipsebuilder].
+  * Create a new maven profile for the java release by creating a patch folder under (eclipse.platform.releng.tychoeclipsebuilder)[eclipse.platform.releng.tychoeclipsebuilder].
     - Name format should be java##patch
     - Update the java and stream versions
     - The `org.eclipse.jdt-feature-dummy/feature.xml` and `org.eclipse.jdt-feature-dummy/pom.xml` files need the version of the `org.eclipse.jdt` jar file. This can be found in the latest milestone builds updates folder, for example:
@@ -64,25 +64,22 @@ When the JDT team is ready they will raise an issue to create new Y and P builds
       the 4.27 M1 jdt version is 3.19.0.v20230104-1800.
     - The plugins for `org.eclipse.jdt.java20patch/feature.xml` will need to be supplied by the JDT team. You can email them or comment on the issue, but only they know what plugins were modified and need to be listed here.
     - The modules listed in the top level pom file (`java##pathc/pom.xml) should match the modified plugins.
-  2. Update the Y-build (buildproperties.txt)[cje-production/Y-build/buildproperties.txt].
+  * Update the Y-build (buildproperties.txt)[cje-production/Y-build/buildproperties.txt].
     - Update the STREAM variables to the current stream
     - Update basebuilder to the previous release
     - Update java version
-  3. Update the P-build (buildproperties.txt)[cje-production/P-build/buildproperties.txt] and (mb300_gatherEclipseParts.sh)[cje-production/P-build/mb300_gatherEclipseParts.sh].
+  * Update the P-build (buildproperties.txt)[cje-production/P-build/buildproperties.txt] and (mb300_gatherEclipseParts.sh)[cje-production/P-build/mb300_gatherEclipseParts.sh].
     - Update the STREAM variables to the current stream
     - Update basebuilder to the previous release
     - Set PATCH_BUILD and PATCH_OR_BRANCH_LABEL to the name of the new maven profile created in step 1
     - PATCH_BUILD_GENERIC in mb300_gatherEclipseParts.sh should be set to the name of the new maven profile
       - The same variable in the normal (mb300_gatherEclipseParts)[cje-production/mbscripts/mb300_gatherEclipseParts.sh] should be updated as well.
-  4. Update and rename the java repository files in (cje-production/streams)[cje-production/streams]
+  * Update and rename the java repository files in (cje-production/streams)[cje-production/streams]
     - Repos without a BETA_JAVA## branch should be set to master
-  5. Update (eclipse-platform-parent/pom.xml)[eclipse-platform-parent/pom.xml]
+  * Update (eclipse-platform-parent/pom.xml)[eclipse-platform-parent/pom.xml]
     - Update all instances of java and java##patch to the new java version
     - `<featureToPatchVersion>` corresponds to the feature version of jdt being replaced, the same version number as `org.eclipse.jdt-feature-dummy/feature.xml` in step 1.
-    - `<versionRangeForPatch>` defines what versions of jdt the patch can be applied to with the intention of invalidating the patch after the next major release. The minimum is the current jdt version, the convention for setting the maximum is `<JDTMajor>.<JDTMinor>.49` and the qualifier is the approximate date of the next major release. So for 4.27 the range would be:
-      ```
-      [3.19.0.v20230104-1800,3.19.49.v20230604-1800)
-      ```
+    - `<versionRangeForPatch>` defines what versions of jdt the patch can be applied to with the intention of invalidating the patch after the next major release. The minimum is the current jdt version, the convention for setting the maximum is `<JDTMajor>.<JDTMinor>.49` and the qualifier is the approximate date of the next major release. So for 4.27 the range would be: `[3.19.0.v20230104-1800,3.19.49.v20230604-1800)`
     - The comparator repo should be the updates folder of the latest release/milestone.
   * Add unit tests for the new java version in (JenkinsJobs/YBuilds)[JenkinsJobs/YBuilds]
   * Add Y and P builds to (Create Jobs)[https://ci.eclipse.org/releng/job/Create%20Jobs/] in Jenkins if they've been removed