Fix up the wording a bit here

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@200016 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Rasmus Lerdorf 2005-11-05 08:08:34 +00:00
parent d4d2fc5caa
commit 7397252121

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.47 $ -->
<!-- $Revision: 1.48 $ -->
<chapter id="language.basic-syntax">
<title>Basic syntax</title>
<sect1 id="language.basic-syntax.phpmode">
@ -183,15 +183,15 @@ if ($expression) {
</informalexample>
</para>
<simpara>
The "one-line" comment styles only comment to the end of
The "one-line" comment styles only comments to the end of
the line or the current block of PHP code, whichever comes first.
This means that HTML code after <literal>// ?&gt;</literal> WILL be printed:
?&gt; skips out of the PHP mode and returns to HTML mode, and
?&gt; breaks out of PHP mode and returns to HTML mode, and
<literal>//</literal> cannot influence that.
If <link linkend="ini.asp-tags">asp_tags</link> configuration directive
If the <link linkend="ini.asp-tags">asp_tags</link> configuration directive
is enabled, it behaves the same with <literal>// %&gt;</literal>.
However, <literal>&lt;/script&gt;</literal> tag doesn't escape PHP mode in
one-line comment.
However, the <literal>&lt;/script&gt;</literal> tag doesn't break out of PHP mode in
a one-line comment.
</simpara>
<para>
<informalexample>
@ -204,9 +204,9 @@ if ($expression) {
</informalexample>
</para>
<simpara>
'C' style comments end by the first encountered <literal>*/</literal>.
You should be careful not to nest 'C' style comments, which can
happen when commenting out large blocks.
'C' style comments end at the first <literal>*/</literal> encountered.
Make sure you don't nest 'C' style comments. It is easy to make this
mistake if you are trying to comment out a large block of code.
</simpara>
<para>
<informalexample>