[exo-jcr-commits] exo-jcr SVN: r1931 - kernel/trunk/exo.kernel.container/src/main/java/org/exoplatform/container/definition.

Author: nfilotto Date: 2010-02-19 15:21:30 -0500 (Fri, 19 Feb 2010) New Revision: 1931 Modified: kernel/trunk/exo.kernel.container/src/main/java/org/exoplatform/container/definition/PortalContainerConfig.java Log: EXOJCR-528: Typo issue in the Javadoc Modified: kernel/trunk/exo.kernel.container/src/main/java/org/exoplatform/container/definition/PortalContainerConfig.java =================================================================== --- kernel/trunk/exo.kernel.container/src/main/java/org/exoplatform/container/definition/PortalContainerConfig.java 2010-02-19 16:57:53 UTC (rev 1930) +++ kernel/trunk/exo.kernel.container/src/main/java/org/exoplatform/container/definition/PortalContainerConfig.java 2010-02-19 20:21:30 UTC (rev 1931) @@ -503,15 +503,15 @@ * a file of type "properties" or "xml". The given path will be interpreted as follows: * <ol> * <li>The path doesn't contain any prefix of type "classpath:", "jar:" or "file:", we - * assume then apply the following rules + * assume that the file could be externalized so we apply the following rules: * <ol> * <li>A file exists at ${exo-conf-dir}/portal/${portalContainerName}/${path}, we * will load this file</li> - * <li>No file exists at the previous path, we then assume that the path can be + * <li>No file exists at the previous path, we then assume that the path cans be * interpreted by the {@link ConfigurationManager}</li> * </ol> * </li> - * <li>The path contains a prefix, we then assume that the path can be interpreted + * <li>The path contains a prefix, we then assume that the path cans be interpreted * by the {@link ConfigurationManager}</li> * </ol> * @param path the path of the external settings to load