[rpms/JUnitParams] epel10: Reflow the description text

[rpms/JUnitParams] epel10: Reflow the description text

[Jerry James]

A new commit has been pushed.

Repo   : rpms/JUnitParams
Branch : epel10
Commit : ddb4e6f310f520fc50b5693048111b84476713fb
Author : Jerry James <loganjerry@gmail.com>
Date   : 2026-01-12T13:29:21-07:00
Stats  : +9/-10 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/JUnitParams/c/ddb4e6f310f520fc50b5693048111b84476713fb?branch=epel10

Log:
Reflow the description text

---
diff --git a/JUnitParams.spec b/JUnitParams.spec
index abc396b..a0cf00f 100644
--- a/JUnitParams.spec
+++ b/JUnitParams.spec
@@ -43,21 +43,20 @@ BuildArch:      noarch
 ExclusiveArch:  %{java_arches} noarch
 
 %description
-The JUnitParams project adds a new runner to JUnit and provides much
-easier and more readable parameterized tests for JUnit >= 4.12.
+The JUnitParams project adds a new runner to JUnit and provides much easier
+and more readable parameterized tests for JUnit >= 4.12.
 
 The main differences with the standard JUnit Parameterized runner are:
 - more explicit - params are in test method params, not class fields
 - less code - you don't need a constructor to set up parameters
 - you can mix parameterized with non-parameterized methods in one class
-- params can be passed as a CSV string or from a parameters provider
-  class
-- parameters provider class can have as many parameters providing
-  methods as you want, so that you can group different cases
-- you can have a test method that provides parameters (no external
-  classes or statics anymore)
-- you can see actual parameter values in your IDE (in JUnit's
-  Parameterized, it's only consecutive numbers of parameters)
+- params can be passed as a CSV string or from a parameters provider class
+- parameters provider class can have as many parameters providing methods as
+  you want, so that you can group different cases
+- you can have a test method that provides parameters (no external classes or
+  statics anymore)
+- you can see actual parameter values in your IDE (in JUnit's Parameterized,
+  it's only consecutive numbers of parameters)
 
 %prep
 %autosetup -n %{name}-%{name}-%{version} -p1