X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=docs%2Fusermanual-opentype-features.xml;h=56eba617fa56db3fa616abecc16733f519c68b58;hb=f0a0bdf96095ae4b3524be4ee4bc32ebe2dfd564;hp=e9ea145344c9ef2c3d4eb467cd15b9a4ac230e8d;hpb=8b9bac85deb2ace750acafa5e0da676f633aadeb;p=platform%2Fupstream%2Fharfbuzz.git

diff --git a/docs/usermanual-opentype-features.xml b/docs/usermanual-opentype-features.xml
index e9ea145..56eba61 100644
--- a/docs/usermanual-opentype-features.xml
+++ b/docs/usermanual-opentype-features.xml
@@ -65,10 +65,10 @@
     </para>
     <para>
       The algorithms
-      used for complex scripts can be quite involved; HarfBuzz tries
+      used for shaping can be quite involved; HarfBuzz tries
       to be compatible with the OpenType Layout specification
       and, wherever there is any ambiguity, HarfBuzz attempts to replicate the
-      output of Microsoft's Uniscribe engine. See the <ulink
+      output of Microsoft's Uniscribe engine, to the extent that is feasible and desirable. See the <ulink
       url="https://docs.microsoft.com/en-us/typography/script-development/standard">Microsoft
       Typography pages</ulink> for more detail.
     </para>
@@ -131,7 +131,7 @@
     </para>
     <para>
       Some OpenType features are defined for the purpose of supporting
-      complex-script shaping, and are automatically activated, but
+      script-specific shaping, and are automatically activated, but
       only when a buffer's script property is set to a script that the
       feature supports.
     </para>