Describe the bug
In the code of the Spirit Instiller recipe for Max/Min Spawn Delay changing, found in file "src/main/java/de/dafuqs/spectrum/recipe/spirit_instiller/dynamic/spawner_manipulation/SpawnerSpawnDelayChangeRecipe.java", the code contains a variety of concerns that could use reworking. A more in depth list can be found below:

• Max and min spawn delay are both checked in an operator && against their minimum values. This leads to spawners not being able to reduce both values to minimum, and the spawners being capped at a higher minimum value for max spawn delay than would otherwise be inferred from the code.
• Code comment specifying that "makes 40 recipes to match the min count for MaxSpawnDelay" is both poorly structured with inaccurate values in the preceding sequence of numbers displaying this reduction behavior, and additionally is incorrect -- the math behind these functions indicate it takes 25 recipes to reach the min count for MinSpawnDelay and 36 to reach the min count for MaxSpawnDelay, but you cannot reach the latter's min count, due to aforementioned.
• Code comment specifying that the sequences of numbers displaying the reduction behavior goes "down to a min of 1 each" is unnecessary, and introduces some potential inaccuracy or misinterpretation -- as the sequence of exponential operations does approach 1, but introducing that min count artificially locks that approach to 20, and even without the min counts, the subtraction of 1 upon no change to the values would decrease that sequence to approaching 0 (1^0.98 results in a value of 1 after short conversion, resulting in that code running subtracting 1 from it, so it would become 0 immediately after, and then remain at 0 indefinitely afterwards).

To Reproduce

1. Look at "src/main/java/de/dafuqs/spectrum/recipe/spirit_instiller/dynamic/spawner_manipulation/SpawnerSpawnDelayChangeRecipe.java".
2. Observe code and code comments.
3. Analyze the code, specifically found on lines 28-29 and 59-81.
4. Notice the discrepancies between the values in the comments and the values in what the code would actually return when ran.
5. Obtain a default spawner.
6. Attempt to craft the recipe (4 midnight chips + spawner + 4 vegetol) repeatedly until the instiller no longer allows.
7. Notice the discrepancies between the min/max spawn delay values on the spawner and between the values listed in code comments and the actual amount of recipes it took.

Expected behavior
Code comments should be accurate and not introduce confusion. Max and min spawn delay should both be able to be decreased to their minimum limits -- either the same number, with both delays able to reach it, or different numbers clearly defined in the code accurately.

Minecraft version
Current compatibility list -- this should be present in any version of Minecraft. I am specifically running 1.20.1 to test in-game.

Mod version
Current. This behavior was introduced in commit 935d027, May 31, 2022, so should be present in all versions except 1.17.1.

Screenshots
The following is a screenshot of the spawner's stats once it cannot be altered further. Notice the max spawn delay and min spawn delay are different, and max spawn delay is not at its minimum value (20).

This should be relatively simple to rework, and I would do so myself if I had more familiarity with GitHub development. Some recommendations below:

• Change the operator && to an operator ||, and that should resolve the difference between the two values, as it would result in both values decreasing further each recipe procession, but would retain the minimum for the min spawn delay value, resulting in only the max spawn delay decreasing further to its minimum value.

return spawnerBlockEntityNbt.getShort("MinSpawnDelay") > MIN_DELAY || spawnerBlockEntityNbt.getShort("MaxSpawnDelay") > MIN_DELAY;

• Change code comments to reflect more accurately the sequence, as shown:

// 800 => 700 => 614 => 540 => 476 => 421 => 373 => 331 => ... => 20
// Makes 25 recipes to match the min count for MinSpawnDelay of 20 ticks (MaxSpawnDelay will be at 52 ticks)
// or 36 recipes to match the min count for MaxSpawnDelay of 20 ticks.

• Alternatively, you could go through the process of changing the MaxSpawnDelay to reduce faster than MinSpawnDelay, such that they reach 20 ticks at the same time. I ran the math on that, keeping it at the current number of recipes, you could change the exponent from 0.98 to 0.97, or increasing both to forty recipes, MaxSpawnDelay from 0.98 to 0.982 and MinSpawnDelay from 0.98 to 0.988. I tried to keep them as round as possible, but forty recipes needs that added decimal place to make it to the minimum in forty recipes without overshooting it.
  However, this alone would be unreliable if any other mod increases/decreases spawner delays. It would be better to keep the operator || even if you did this more effective route, I would suggest.