New upstream version 20200110

[perltidy.git] / docs / tutorial.html

diff --git a/docs/tutorial.html b/docs/tutorial.html
index 7031763bedeaa03b8e66e6ea6990fb3a6b46504e..4e11efc41034558d53baf4db57dcc37a74e2575d 100644 (file)
--- a/docs/tutorial.html
+++ b/docs/tutorial.html
@@ -136,7 +136,7 @@
 
 <pre><code> perltidy *.pl</code></pre>
 
-<p>and in this case, each of the output files will be have a name equal to the input file with the extension <i>.tdy</i> appended. If you decide that the formatting is acceptable, you will want to backup your originals and then remove the <i>.tdy</i> extensions from the reformatted files. There is an powerful perl script called <code>rename</code> that can be used for this purpose; if you don&#39;t have it, you can find it for example in <b>The Perl Cookbook</b>.</p>
+<p>and in this case, each of the output files will be have a name equal to the input file with the extension <i>.tdy</i> appended. If you decide that the formatting is acceptable, you will want to backup your originals and then remove the <i>.tdy</i> extensions from the reformatted files. There is a powerful perl script called <code>rename</code> that can be used for this purpose; if you don&#39;t have it, you can find it for example in <b>The Perl Cookbook</b>.</p>
 
 <p>If you find that the formatting done by perltidy is usually acceptable, you may want to save some effort by letting perltidy do a simple backup of the original files and then reformat them in place. You specify this with a <b>-b</b> flag. For example, the command</p>