summaryrefslogtreecommitdiff
path: root/README.SUBMITTING_PATCH
diff options
context:
space:
mode:
authorMarcus Boerger <helly@php.net>2003-12-22 23:45:53 (GMT)
committerMarcus Boerger <helly@php.net>2003-12-22 23:45:53 (GMT)
commit8a072165f573e8023e4473d7da6c2cdb1e088b7f (patch)
treecfbb25d37d68cf25c85959cc9e787bae2a751051 /README.SUBMITTING_PATCH
parent3aad8267a8df034055132573401966be4cb6c59b (diff)
downloadphp-8a072165f573e8023e4473d7da6c2cdb1e088b7f.tar.gz
Typos found by Petras Kudaras.
Diffstat (limited to 'README.SUBMITTING_PATCH')
-rw-r--r--README.SUBMITTING_PATCH4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.SUBMITTING_PATCH b/README.SUBMITTING_PATCH
index 5b9516e..04847d7 100644
--- a/README.SUBMITTING_PATCH
+++ b/README.SUBMITTING_PATCH
@@ -90,7 +90,7 @@ Please add the prefix "[PATCH]" to your email subject and make sure
to include the patch as a MIME attachment even if it is short.
NOTE: only MIME attachments of type 'text/*' are accepted. The
- easiest way to acclomplish this, is to make the extension
+ easiest way to accomplish this, is to make the extension
'.txt'.
Test scripts should be included in the same email.
@@ -100,7 +100,7 @@ Finally, add the bug Id(s) which can be closed by your patch, if any.
What happens after you submit your patch
---------------------------------------
+----------------------------------------
If your patch is easy to review and has obviously no side-effects,
it might take up to a few hours until someone commits it.