Fixed closed parenthesis '.)' -> ').'

blue-eyes · fabpot · commit 3992be5226ec · 2010-11-22T08:33:55.000+01:00
diff --git a/contributing/code/patches.rst b/contributing/code/patches.rst
@@ -67,7 +67,7 @@ topic branch:
     ticket number is a good convention for bug fixes).
 
 The above command automatically switches the code to the newly created branch
-(check the branch you are working on with `git branch`.)
+(check the branch you are working on with `git branch`).
 
 Work on the code as much as you want and commit as much as you want; but keep
 in mind the following:
diff --git a/guides/cache/http.rst b/guides/cache/http.rst
@@ -60,7 +60,7 @@ header when none is set by the developer by following these rules:
 
 * But if at least one ``Cache-Control`` directive is set, and no 'public' or
   ``private`` directives have been explicitly added, Symfony2 adds the
-  ``private`` directive automatically (except when ``s-maxage`` is set.)
+  ``private`` directive automatically (except when ``s-maxage`` is set).
 
 .. tip::
 
@@ -232,7 +232,7 @@ issue. Under this model, you mainly save bandwidth as the representation is
 not sent twice to the same client (a 304 response is sent instead). But if you
 design your application carefully, you might be able to get the bare minimum
 data needed to send a 304 response and save CPU also; and if needed, perform
-the more heavy tasks (see below for an implementation example.)
+the more heavy tasks (see below for an implementation example).
 
 .. index::
    single: Cache; Etag header
@@ -399,7 +399,7 @@ Public vs Private Responses
 
 As explained at the beginning of this document, Symfony2 is very conservative
 and makes all Responses private by default (the exact rules are described
-there.)
+there).
 
 If you want to use a shared cache, you must remember to explicitly add the
 ``public`` directive to ``Cache-Control``::
@@ -619,7 +619,7 @@ standalone is ``false``.
 
     Symfony2 detects if a gateway cache supports ESI via another Akamaï
     specification that is supported out of the box by the Symfony2 reverse
-    proxy (a working configuration for Varnish is also provided below.)
+    proxy (a working configuration for Varnish is also provided below).
 
 For the ESI include tag to work properly, you must define the ``_internal``
 route:
diff --git a/guides/security/authentication.rst b/guides/security/authentication.rst
@@ -75,7 +75,7 @@ basic authentication:
 Each firewall configuration is activated when the incoming request matches the
 regular expression defined by the ``pattern`` setting. This pattern must match
 the request path info (``preg_match('#^'.PATTERN_VALUE.'$#',
-$request->getPathInfo())``.)
+$request->getPathInfo())``).
 
 .. tip::
 
@@ -155,7 +155,7 @@ X.509 certificate, an Authorization HTTP header, or use a form to login.
     authentication mechanisms, Symfony2 automatically defines a default entry
     point (in the example above, the login form; but if the user send an
     Authorization HTTP header with wrong credentials, Symfony2 will use the
-    HTTP basic entry point.)
+    HTTP basic entry point).
 
 .. note::
 
@@ -499,7 +499,7 @@ working configuration for Apache:
     </VirtualHost>
 
 By default, the username is the email declared in the certificate (the value
-of the ``SSL_CLIENT_S_DN_Email`` environment variable.)
+of the ``SSL_CLIENT_S_DN_Email`` environment variable).
 
 .. tip::
 
@@ -549,7 +549,7 @@ restricted by a more restrictive access control rule:
 As anonymous users are authenticated, the ``isAuthenticated()`` method returns
 ``true``. To check is the user is anonymous, check for the
 ``IS_AUTHENTICATED_ANONYMOUSLY`` role instead (note that all non-anonymous
-users have the ``IS_AUTHENTICATED_FULLY`` role.)
+users have the ``IS_AUTHENTICATED_FULLY`` role).
 
 .. index::
    single: Security; Stateless Authentication
@@ -606,7 +606,7 @@ Impersonating a User
 
 Sometimes, it's useful to be able to switch from one user to another without
 having to logout and login again (for instance when you are debugging or try
-to understand a bug a user see and you cannot reproduce.) This can be easily
+to understand a bug a user see and you cannot reproduce). This can be easily
 done by activating the ``switch-user`` listener:
 
 .. configuration-block::
diff --git a/guides/security/overview.rst b/guides/security/overview.rst
@@ -9,7 +9,7 @@ providing authentication and authorization.
 
 *Authentication* ensures that the user is who he claims to be. *Authorization*
 refers to the process of deciding whether a user is allowed to perform an
-action or not (authorization comes after authentication.)
+action or not (authorization comes after authentication).
 
 This document is a quick overview of these main concepts, but the real power
 is distilled in three other documents: :doc:`Users </guides/security/users>`,
diff --git a/guides/security/users.rst b/guides/security/users.rst
@@ -102,7 +102,7 @@ For most use case, use
 
 When encoding your passwords, it's better to also define a unique salt per user
 (the ``getSalt()`` method can return the primary key if users are persisted in
-a database for instance.)
+a database for instance).
 
 .. index::
    single: Security; AdvancedAccountInterface
@@ -416,7 +416,7 @@ Roles
 A User can have as many roles as needed. Roles are usually defined as strings,
 but they can be any object implementing
 :class:`Symfony\\Component\\Security\\Role\\RoleInterface` (roles are always
-objects internally.) Roles defined as strings should begin with the ``ROLE_``
+objects internally). Roles defined as strings should begin with the ``ROLE_``
 prefix to be automatically managed by Symfony2.
 
 The roles are used by the access decision manager to secure resources. Read
diff --git a/guides/translation.rst b/guides/translation.rst
@@ -90,7 +90,7 @@ Store translations for messages found in a bundle under the
 
 Each message file must be named according to the following pattern:
 ``domain.locale.loader`` (the domain name, followed by a dot (``.``), followed
-by the locale name, followed by a dot (``.``), followed by the loader name.)
+by the locale name, followed by a dot (``.``), followed by the loader name).
 
 The loader can be the name of any registered loader. By default, Symfony2
 provides the following loaders:
