tools removed whitespaces from Comment-Based Help

tools/Add-FolderOnPath.ps1

@@ -313,17 +313,11 @@ process {
   Prepends or appends a path to the defined environment variable.
 
  .Description
-  `Add-FolderOnPath` script prepends or appends a path to the environment variable defined by
-  the Variable parameter or PATH env. variable by default. A path is prepended by default or
-  you can use the Append parameter to append a path. You can also use the LibraryPath parameter
-  that adds a path to the `LD_LIBRARY_PATH` environment variable.
+  `Add-FolderOnPath` script prepends or appends a path to the environment variable defined by the Variable parameter or PATH env. variable by default. A path is prepended by default or you can use the Append parameter to append a path. You can also use the LibraryPath parameter that adds a path to the `LD_LIBRARY_PATH` environment variable.
 
-  The RestorePath parameter restores a current environment to its original state. It tracks all
-  the changed environment variables and after the call, all the changed env. variables will be
-  restored at once.
+  The RestorePath parameter restores a current environment to its original state. It tracks all the changed environment variables and after the call, all the changed env. variables will be restored at once.
 
-  A path will not be added when an environment variable already contains this path. You can
-  add more paths add once and the script also works on Unix systems.
+  A path will not be added when an environment variable already contains this path. You can add more paths add once and the script also works on Unix systems.
 
  .Parameter Path
   Specifies the folder to add on the system path, is pwd by default.

tools/Get-VcpkgHash.ps1

@@ -109,9 +109,7 @@ finally {
   Computes the SHA-512 hash of a specified branch or git reference object
 
  .Description
-  Computes the hash of a specified branch or git reference object. By default, it computes
-  the SHA-512 hash. The output will be the computed hash for the given git object displayed directly
-  on the console.
+  Computes the hash of a specified branch or git reference object. By default, it computes the SHA-512 hash. The output will be the computed hash for the given git object displayed directly on the console.
 
   Prints error message to the error stream and exits with the error code 1 if the download fails.
 
@@ -141,8 +139,7 @@ finally {
 
  .INPUTS
   System.String
-    You can pipe a branch for which to download the package archive and compute the SHA-512 hash
-    (works with a commit ID too).
+    You can pipe a branch for which to download the package archive and compute the SHA-512 hash (works with a commit ID too).
 
  .OUTPUTS
   The computed SHA-512 hash for the given git object (branch or ref).

tools/deploy.ps1

@@ -1707,9 +1707,7 @@ Invoke-MergeDevelopAndDeploy -Message 'Vcpkg ports were updated and deployed suc
   The TinyORM library bumping version numbers and deployment script
 
  .Description
-  The `deploy.ps1` script helps with bumping version numbers for all libraries and deploying these
-  changes to the `main` branch. It also outputs all the available information and allows to confirm
-  or cancel future processing.
+  The `deploy.ps1` script helps with bumping version numbers for all libraries and deploying these changes to the `main` branch. It also outputs all the available information and allows to confirm or cancel future processing.
 
   It does the following actions:
 
@@ -1748,15 +1746,9 @@ Invoke-MergeDevelopAndDeploy -Message 'Vcpkg ports were updated and deployed suc
   - prepare the vcpkg commit message
   - do the commit, merge to the `main` branch (ff-only), and push to the `origin/main`
 
-  The deployment is not possible without bumping the `TinyOrm` library version number because a git
-  tag must be created. That means that bumping only the `tom`, `TinyDrivers`, `TinyMySql`, or `TinyUtils`
-  isn't possible. This used to be possible, but not anymore because git tags are created during
-  deployment.
+  The deployment is not possible without bumping the `TinyOrm` library version number because a git tag must be created. That means that bumping only the `tom`, `TinyDrivers`, `TinyMySql`, or `TinyUtils` isn't possible. This used to be possible, but not anymore because git tags are created during deployment.
 
-  There is a second mode that allows to completely skip bumping version numbers and in this case
-  is possible to deploy the vcpkg ports only. The vcpkg ports will use the git commit ID
-  of the main branch for the vcpkg_from_github REF option in this case. The first approval question
-  allows you to select this so-called second mode.
+  There is a second mode that allows to completely skip bumping version numbers and in this case is possible to deploy the vcpkg ports only. The vcpkg ports will use the git commit ID of the main branch for the vcpkg_from_github REF option in this case. The first approval question allows you to select this so-called second mode.
 
  .INPUTS
   Nothing.