remove forced new lines

Author: rlnt

wikis/energymeter/docs/basics.md

@@ -6,15 +6,9 @@ Welcome to the **Energy Meter** mod!
 
 <img src="/../img/logo.png" width="300" style="float:right; margin-left:10px;" />
 
-Energy Meter is a small content mod that adds a block called the Energy Meter which allows you to measure energy flow rates.
-The block functions as a cable: incoming requests are simply forwarded to the outputs. All values of these requests are stored and used at
-a configurable interval to calculate the flow rate.
+Energy Meter is a small content mod that adds a block called the Energy Meter which allows you to measure energy flow rates. The block functions as a cable: incoming requests are simply forwarded to the outputs. All values of these requests are stored and used at a configurable interval to calculate the flow rate.
 
-In addition to a comprehensive user interface, the block also features a digital display on its front. The current rate can be checked
-there at any time. The display can be rotated in any direction, including upwards and downwards. Since the front of the Energy Meter is
-used for the display, only the remaining five sides can be configured as input or output.
+In addition to a comprehensive user interface, the block also features a digital display on its front. The current rate can be checked there at any time. The display can be rotated in any direction, including upwards and downwards. Since the front of the Energy Meter is used for the display, only the remaining five sides can be configured as input or output.
 
-To review the rates of previous intervals, the Energy Meter’s user interface also includes a graph view. This shows the measurements of
-the last 10 intervals and can also be paused. The interface provides many additional configuration options. Besides different
-measurement methods, both the measurement interval and the calculation mode can be adjusted.<br/>
+To review the rates of previous intervals, the Energy Meter’s user interface also includes a graph view. This shows the measurements of the last 10 intervals and can also be paused. The interface provides many additional configuration options. Besides different measurement methods, both the measurement interval and the calculation mode can be adjusted.<br/>
 You can find more details on the [Interface](interface.md) page.

wikis/energymeter/docs/interface.md

@@ -3,29 +3,18 @@
 > [!WARNING] NOTE
 > This wiki is for Energy Meter for Minecraft 1.21.1 and above. For previous versions, please refer to the [old wiki](https://github.com/AlmostReliable/energymeter/wiki).
 
-If you have previously used **Energy Meter** with Minecraft 1.20 or earlier, you will notice that several things have changed. The mod has been
-completely rewritten from the ground up and now includes many technical improvements as well as new features.
+If you have previously used **Energy Meter** with Minecraft 1.20 or earlier, you will notice that several things have changed. The mod has been completely rewritten from the ground up and now includes many technical improvements as well as new features.
 
-Most importantly, it is now possible to have multiple inputs and outputs instead of only a single input as before. This was one of the biggest
-criticisms of the old version. Since the calculation system was rebuilt from scratch, it was finally possible to remove this limitation.
+Most importantly, it is now possible to have multiple inputs and outputs instead of only a single input as before. This was one of the biggest criticisms of the old version. Since the calculation system was rebuilt from scratch, it was finally possible to remove this limitation.
 
-Another frequently requested feature, though not easy to implement, was the ability to limit the flow rate of the Energy Meter. The block no
-longer behaves like an unlimited cable when a limit is configured in the GUI. Naturally, the limit also supports multiple inputs. In this case,
-all inputs are limited collectively rather than individually.
+Another frequently requested feature, though not easy to implement, was the ability to limit the flow rate of the Energy Meter. The block no longer behaves like an unlimited cable when a limit is configured in the GUI. Naturally, the limit also supports multiple inputs. In this case, all inputs are limited collectively rather than individually.
 
-More information is now available as well. The interface now displays the total throughput the Energy Meter has processed so far. This accumulated
-value can be reset at the press of a button in the GUI. It is also easier to see which mode the Energy Meter is currently operating in. Previously
-used toggleable labels have been replaced with convenient radio buttons. This makes it easier not only to see the currently selected option but also
-all available options. Related settings are also grouped together, improving clarity and usability.
+More information is now available as well. The interface now displays the total throughput the Energy Meter has processed so far. This accumulated value can be reset at the press of a button in the GUI. It is also easier to see which mode the Energy Meter is currently operating in. Previously used toggleable labels have been replaced with convenient radio buttons. This makes it easier not only to see the currently selected option but also all available options. Related settings are also grouped together, improving clarity and usability.
 
-The input fields have also been completely redesigned. They now provide feedback for invalid values and support mathematical expressions. The
-preliminary result is displayed in a small tooltip.
+The input fields have also been completely redesigned. They now provide feedback for invalid values and support mathematical expressions. The preliminary result is displayed in a small tooltip.
 
-Another new feature is the graph view. It displays the values of previous intervals in a clear visual format. The graph can also be paused
-for closer inspection.
+Another new feature is the graph view. It displays the values of previous intervals in a clear visual format. The graph can also be paused for closer inspection.
 
-Finally, new configuration options have also been added. It is now possible to define the default interval frequency that every Energy Meter
-uses when placed. Additionally, you can configure whether Energy Meters are allowed to connect to each other.
+Finally, new configuration options have also been added. It is now possible to define the default interval frequency that every Energy Meter uses when placed. Additionally, you can configure whether Energy Meters are allowed to connect to each other.
 
-Since the mod is still in the beta phase, additional features will be added over time. Planned features include things like **ComputerCraft integration**
-and interactions with **Redstone**. For a more detailed explanation of all features and the user interface, please refer to the other pages of this wiki.
+Since the mod is still in the beta phase, additional features will be added over time. Planned features include things like **ComputerCraft integration** and interactions with **Redstone**. For a more detailed explanation of all features and the user interface, please refer to the other pages of this wiki.

wikis/energymeter/docs/whats_new.md

@@ -3,8 +3,7 @@
 > [!WARNING]
 > This wiki is still work in progress! It just lists all examples for now without further explanation.
 
-This mod is an add-on for [KubeJS](https://github.com/KubeJS-Mods/KubeJS) to add support for [Actually Additions](https://github.com/Ellpeck/ActuallyAdditions).
-It offers easy creation of new recipes, modification of existing ones, and a custom event to modify empowerer behavior.
+This mod is an add-on for [KubeJS](https://github.com/KubeJS-Mods/KubeJS) to add support for [Actually Additions](https://github.com/Ellpeck/ActuallyAdditions). It offers easy creation of new recipes, modification of existing ones, and a custom event to modify empowerer behavior.
 
 Useful links:
 

wikis/kubejs-actuallyadditions/docs/index.md

@@ -41,8 +41,7 @@ A `Result` is a convenience type added by EnderIO that supports `ItemStack`s wit
 
 ## Examples
 
-This binding is intended to be used inside [Fire Crafting recipes](../misc/firecrafting.md). Pass it to the `results` parameter to define complex outputs. You
-can also store the outputs in a variable and reuse them in multiple recipes.
+This binding is intended to be used inside [Fire Crafting recipes](../misc/firecrafting.md). Pass it to the `results` parameter to define complex outputs. You can also store the outputs in a variable and reuse them in multiple recipes.
 
 ```js
 ServerEvents.recipes(event => {

wikis/kubejs-enderio/docs/binding/firecraftingresult.md

@@ -17,8 +17,7 @@ A `BonusType` specifies the behavior of Grinding Balls in Sag Mill recipes.
 
 ## Examples
 
-This binding is intended to be used inside [Sag Mill recipes](../machine/sagmill.md). Pass it to the `bonus` parameter to define the bonus type of the recipe.
-It's also possible to use the strings `"NONE"`, `"CHANCE_ONLY"`, and `"MULTIPLY_OUTPUT"` instead of the binding.
+This binding is intended to be used inside [Sag Mill recipes](../machine/sagmill.md). Pass it to the `bonus` parameter to define the bonus type of the recipe. It's also possible to use the strings `"NONE"`, `"CHANCE_ONLY"`, and `"MULTIPLY_OUTPUT"` instead of the binding.
 
 ```js
 ServerEvents.recipes(event => {

wikis/kubejs-enderio/docs/binding/sagmillbonus.md

@@ -2,8 +2,7 @@
 
 The `SagMillOutput` is a utility binding that allows you to easily create `OutputItem`s for [Sag Mill recipes](../machine/sagmill.md).
 
-An `OutputItem` is a convenience type added by EnderIO that supports `ItemStack`s and `TagKey`s. Its main purpose is to allow the usage of tags
-as outputs in Sag Mill recipes. This way, EnderIO doesn't need to add a material for every compat recipe they have. Instead they can use the respective tag.
+An `OutputItem` is a convenience type added by EnderIO that supports `ItemStack`s and `TagKey`s. Its main purpose is to allow the usage of tags as outputs in Sag Mill recipes. This way, EnderIO doesn't need to add a material for every compat recipe they have. Instead they can use the respective tag.
 
 It also supports chance-based outputs which can be useful for something like byproducts.
 
@@ -46,8 +45,7 @@ It also supports chance-based outputs which can be useful for something like byp
 
 ## Examples
 
-This binding is intended to be used inside [Sag Mill recipes](../machine/sagmill.md). Pass it to the `outputs` parameter to define complex outputs. You
-can also store the outputs in a variable and reuse them in multiple recipes.
+This binding is intended to be used inside [Sag Mill recipes](../machine/sagmill.md). Pass it to the `outputs` parameter to define complex outputs. You can also store the outputs in a variable and reuse them in multiple recipes.
 
 ```js
 ServerEvents.recipes(event => {

wikis/kubejs-enderio/docs/binding/sagmilloutput.md

@@ -15,8 +15,7 @@ A `Mode` specifies the behavior of the tank in the recipe.
 
 ## Examples
 
-This binding is intended to be used inside [Tank recipes](../machine/tank.md). Pass it to the `mode` parameter to define the mode of the recipe.
-It's also possible to use the strings `"FILL"` and `"EMPTY"` instead of the binding.
+This binding is intended to be used inside [Tank recipes](../machine/tank.md). Pass it to the `mode` parameter to define the mode of the recipe. It's also possible to use the strings `"FILL"` and `"EMPTY"` instead of the binding.
 
 ```js
 ServerEvents.recipes(event => {

wikis/kubejs-enderio/docs/binding/tankmode.md

@@ -5,8 +5,7 @@ This registry event extension allows you to register custom Capacitors. Capacito
 > [!WARNING] NOTE
 > This event extension only exists since mod version 1.21.1-0.12.0, release date: 2026-02-18.
 
-**It is a startup event and not reloadable!**
-Keep in mind that startup events have to be located inside the `kubejs/startup_scripts` folder.
+**It is a startup event and not reloadable!** Keep in mind that startup events have to be located inside the `kubejs/startup_scripts` folder.
 
 ## Overview
 

wikis/kubejs-enderio/docs/event/capacitorregistry.md

@@ -2,8 +2,7 @@
 
 This event allows you to register custom conduits.
 
-**It is a server event and reloadable!**
-Keep in mind that server events have to be located inside the `kubejs/server_scripts` folder.
+**It is a server event and reloadable!** Keep in mind that server events have to be located inside the `kubejs/server_scripts` folder.
 
 > [!WARNING] NOTE
 > The Conduits have been reworked by the EnderIO team in version 8.2.0. Previously, the functions to register the conduits required some more properties. If you need help with that, join the Discord or take a look at the source code before version 8.2.0.
@@ -33,11 +32,9 @@ EnderIOEvents.conduits(event => {
 })
 ```
 
-After that, use one of the following methods to register the respective conduit type. All conduits need an `id` that is used as the registry name and a
-`name` that is used for the automatic language file entry generation.
+After that, use one of the following methods to register the respective conduit type. All conduits need an `id` that is used as the registry name and a `name` that is used for the automatic language file entry generation.
 
-The custom conduit will be part of the normal EnderIO Conduits creative tab. Recipes are **not** generated automatically. You have to add a recipe
-for your custom conduits yourself! You sometimes need to rejoin the world to see the new conduits. A game restart is not necessary.
+The custom conduit will be part of the normal EnderIO Conduits creative tab. Recipes are **not** generated automatically. You have to add a recipe for your custom conduits yourself! You sometimes need to rejoin the world to see the new conduits. A game restart is not necessary.
 
 ### Item Conduit
 
@@ -96,21 +93,17 @@ EnderIOEvents.conduits(event => {
 
 ## Texture
 
-After registering the custom conduit inside the event, the language file as well as the model file are automatically generated. The
-only things you have to provide are the textures.
+After registering the custom conduit inside the event, the language file as well as the model file are automatically generated. The only things you have to provide are the textures.
 
 ### Block Texture
 
-For the block of the conduit, the texture file needs to be placed inside the following directory:
-`kubejs/assets/enderio/textures/block/conduit`
+For the block of the conduit, the texture file needs to be placed inside the following directory: `kubejs/assets/enderio/textures/block/conduit`
 
-It needs to have the same name as the `id` parameter you used when registering the custom conduit. Make sure it's a valid `.png` file.
-You can download a template PSD file [here](https://github.com/AlmostReliable/kubejs-enderio/wiki/files/conduit.psd).
+It needs to have the same name as the `id` parameter you used when registering the custom conduit. Make sure it's a valid `.png` file. You can download a template PSD file [here](https://github.com/AlmostReliable/kubejs-enderio/wiki/files/conduit.psd).
 
 ### Conduit Icon
 
-For the icon inside the conduit GUI, you need to provide an additional texture file. It has to be placed in the following directory:
-`kubejs/assets/enderio/textures/conduit_icon`
+For the icon inside the conduit GUI, you need to provide an additional texture file. It has to be placed in the following directory: `kubejs/assets/enderio/textures/conduit_icon`
 
 Once again, the texture should have the same name as your conduit `id`. Make sure to crop the texture accordingly so it only consists of the actual icon.