Typographical quotation marks and en dashes

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@17325 44c647ce-9c0f-0410-b52a-842ac1e357ba

documentation/manual/en/ref/installation.xml

@@ -13,7 +13,7 @@
         Installing Zend Framework is extremely simple. Once you have downloaded and extracted the
         framework, you should add the <filename>/library</filename> folder in the distribution to
         the beginning of your include path. You may also want to move the library folder
-        to another- possibly shared- location on your file system.
+        to another – possibly shared – location on your file system.
     </para>
 
     <itemizedlist>
@@ -64,10 +64,10 @@
                 An
                 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html">
                 externals definition</ulink> is quite convenient for developers already using
-                <acronym>SVN</acronym> to manage their application's working copies.
+                <acronym>SVN</acronym> to manage their application’s working copies.
             </para>
             <para>
-                The <acronym>URL</acronym> for the trunk of Zend Framework's <acronym>SVN</acronym>
+                The <acronym>URL</acronym> for the trunk of Zend Framework’s <acronym>SVN</acronym>
                 repository is: <ulink
                     url="http://framework.zend.com/svn/framework/standard/trunk">
                     http://framework.zend.com/svn/framework/standard/trunk</ulink>
@@ -81,7 +81,7 @@
         <ulink url="http://www.php.net/manual/en/configuration.changes.php">
         several ways to achieve this</ulink>, your <acronym>PHP</acronym>
         <ulink url="http://www.php.net/manual/en/ini.core.php#ini.include-path">include_path</ulink>
-        needs to contain the path to Zend Framework's library.
+        needs to contain the path to Zend Framework’s library.
     </para>
 
     <para>

documentation/manual/en/ref/overview.xml

@@ -9,7 +9,7 @@
         with PHP 5. Zend Framework is implemented using 100% object-oriented code. The component
         structure of Zend Framework is somewhat unique; each component is designed
         with few dependencies on other components. This loosely coupled architecture allows
-        developers to use components individually. We often call this a "use-at-will" design.
+        developers to use components individually. We often call this a “use-at-will” design.
     </para>
     <para>
         While they can be used separately, Zend Framework components in the standard library form a
@@ -21,11 +21,11 @@
         <classname>Zend_Auth</classname> and <classname>Zend_Acl</classname>, provide user
         authentication and authorization against all common credential stores. Still others
         implement client libraries to simply access to the most popular web services available.
-        Whatever your application needs are, you're likely to find a Zend Framework component that
+        Whatever your application needs are, you’re likely to find a Zend Framework component that
         can be used to dramatically reduce development time with a thoroughly tested foundation.
     </para>
     <para>
-        The principal sponsor of the project 'Zend Framework' is <ulink url="http://www.zend.com">
+        The principal sponsor of the project ‘Zend Framework’ is <ulink url="http://www.zend.com">
         Zend Technologies</ulink>, but many companies have contributed components or significant
         features to the framework. Companies such as Google, Microsoft, and StrikeIron have
         partnered with Zend to provide interfaces to web services and other technologies that they

documentation/manual/en/ref/requirements.xml

@@ -14,11 +14,11 @@
             additional extensions or web server features; in most cases the framework can be used
             without them, although performance may suffer or ancillary features may not be fully
             functional. An example of such a dependency is mod_rewrite in an Apache environment,
-            which can be used to implement "pretty <acronym>URL</acronym>'s" like
-            "<filename>http://www.example.com/user/edit</filename>". If mod_rewrite is not enabled,
-            Zand Framework can be configured to support <acronym>URL</acronym>'s such as
-            "<command>http://www.example.com?controller=user&amp;action=edit</command>". Pretty
-            <acronym>URL</acronym>'s may be used to shorten <acronym>URL</acronym>'s for textual
+            which can be used to implement “pretty <acronym>URL</acronym>’s” like
+            “<filename>http://www.example.com/user/edit</filename>”. If mod_rewrite is not enabled,
+            Zand Framework can be configured to support <acronym>URL</acronym>’s such as
+            “<command>http://www.example.com?controller=user&amp;action=edit</command>”. Pretty
+            <acronym>URL</acronym>’s may be used to shorten <acronym>URL</acronym>’s for textual
             representation or search engine optimization (<acronym>SEO</acronym>), but they do not
             directly affect the functionality of the application.
         </para>
@@ -47,15 +47,15 @@
             <para>
                 You will find a table listing all extensions typically found in
                 <acronym>PHP</acronym> and how they are used in Zend Framework below. You should
-                verify that the extensions on which Zend Framework components you'll be using in
+                verify that the extensions on which Zend Framework components you’ll be using in
                 your application are available in your <acronym>PHP</acronym> environments. Many
                 applications will not require every extension listed below.
             </para>
 
             <para>
-                A dependency of type "hard" indicates that the components or classes
+                A dependency of type “hard” indicates that the components or classes
                 cannot function properly if the respective extension is not available,
-                while a dependency of type "soft" indicates that the component may use
+                while a dependency of type “soft” indicates that the component may use
                 the extension if it is available but will function properly if it is not.
                 Many components will automatically use certain extensions if they are available
                 to optimize performance but will execute code with similar functionality in the
@@ -78,9 +78,9 @@
             </para>
 
             <para>
-                A dependency of type "hard" indicates that the components or classes
+                A dependency of type “hard” indicates that the components or classes
                 cannot function properly if the respective extension is not available,
-                while a dependency of type "soft" indicates that the component may use
+                while a dependency of type “soft” indicates that the component may use
                 the extension if it is available but will function properly if it is not.
                 Many components will automatically use certain extensions if they are available
                 to optimize performance but will execute code with similar functionality in the
@@ -102,12 +102,12 @@
             </para>
 
             <para>
-                A dependency of type "hard" indicates that the components or classes
+                A dependency of type “hard” indicates that the components or classes
                 cannot function properly if the respective dependent component is not available,
-                while a dependency of type "soft" indicates that the component may need
+                while a dependency of type “soft” indicates that the component may need
                 the dependent component in special situations or with special adapters.
-                At last a dependency of type "fix" indicated that this components or classes are
-                in any case used by subcomponents, and a dependency of type "sub" indicates that
+                At last a dependency of type “fix” indicated that this components or classes are
+                in any case used by subcomponents, and a dependency of type “sub” indicates that
                 these components can be used by subcomponents in special situations or with special
                 adapters.
             </para>