From 2181e740570d5794b98a0295ed898b900f4e87f6 Mon Sep 17 00:00:00 2001
From: Moriyoshi Koizumi <moriyoshi@php.net>
Date: Sat, 13 Mar 2004 23:41:01 +0000
Subject: [PATCH] - Typo..

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@153604 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/mbstring/ini.xml | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/reference/mbstring/ini.xml b/reference/mbstring/ini.xml
index fc1490919b..f93f1877ba 100644
--- a/reference/mbstring/ini.xml
+++ b/reference/mbstring/ini.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.10 $ -->
+<!-- $Revision: 1.11 $ -->
 <section id="mbstring.configuration">
  &reftitle.runtime;
  &extension.runtime;
@@ -137,10 +137,11 @@
   used by browsers.
  </para>
  <para>
-  Although browsers are enough to detect the character encoding
-  of a given HTML document by using heuristics, it would be better to set the
-  <literal>charset</literal> parameter in the <literal>Content-Type</literal>
-  HTTP header to the appropriate value by <function>header</function> or
+  Although popular browsers are capable of giving a reasonably accurate guess
+  to the character encoding of a given HTML document, it would be better to
+  set the <literal>charset</literal> parameter in the
+  <literal>Content-Type</literal> HTTP header to the appropriate value by
+  <function>header</function> or
   <link linkend="ini.sect.data-handling">default_charset</link> ini setting.
  </para>
  <para>