com web/bugs: Fix typos in how to report info: www/how-to-report.php
| From: | Christoph Michael Becker | Date: | Tue, 24 Jul 2018 14:07:18 +0000 |
| Subject: | com web/bugs: Fix typos in how to report info: www/how-to-report.php | ||
| Groups: | php.webmaster | ||
| Request: | Send a blank email to php-webmaster+get-27178@lists.php.net to get a copy of this message | ||
Commit: d5644bc6d3a4997ead7b35af9c19301a19648293
Author: Peter Kokot <peterkokot@gmail.com> Fri, 29 Jun 2018 19:24:13 +0200
Committer: Christoph M. Becker <cmbecker69@gmx.de> Tue, 24 Jul 2018 16:07:18 +0200
Parents: e9b937bb165a27b04149d9a8f0921fb3441afd05
Branches: master
Link: http://git.php.net/?p=web/bugs.git;a=commitdiff;h=d5644bc6d3a4997ead7b35af9c19301a19648293
Log:
Fix typos in how to report info
Changed paths:
M www/how-to-report.php
Diff:
diff --git a/www/how-to-report.php b/www/how-to-report.php
index 50105c8..c73f91e 100644
--- a/www/how-to-report.php
+++ b/www/how-to-report.php
@@ -12,7 +12,7 @@ response_header('How to Report a Bug');
<h1>How to Report a Bug</h1>
-<p>There is a large number of PHP users. There is a much small number of people
+<p>There is a large number of PHP users. There is a much smaller number of people
who actually develop the PHP language and extensions. There is an even smaller
number of people who actively fix bugs reported by users.</p>
@@ -47,7 +47,7 @@ get, and what you actually got, we don't have to guess.</p>
<h2>Always search the bug database first.</h2>
-<p>Advice so good, we'll repeat it twice. Always <a
+<p>Advice is so good, we'll repeat it twice. Always <a
href="search.php">search</a> the bug database first. As we said above,
there's
a lot of users of PHP. The odds are good that if you've found a problem,
someone else has found it, too. If you spend a few minutes of your time making
@@ -77,10 +77,10 @@ as a feature request.)</p>
<li>
When you provide code that demonstrates the problem, it should almost
never be more than ten lines long. Anything longer probably contains a
- lot of code that has nothing to do with the problem, which just makes
- it take longer to figure out the real problem. (But don't forget to make
+ lot of code that has nothing to do with the problem, which just increases
+ the time to figure out the real problem. (But don't forget to make
sure that your code still demonstrates the bug you're reporting and
- doesn't have some other problem because you've accidently trimmed out
+ doesn't have some other problem because you've accidentally trimmed out
something you thought wasn't important but was!)
</li>
<li>