svn commit: r1497153 - /maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt

[ol...@apache.org]

Author: olamy
Date: Wed Jun 26 23:05:44 2013
New Revision: 1497153

URL: http://svn.apache.org/r1497153
Log:
fix apt file

Modified:
    maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt

Modified: maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt?rev=1497153&r1=1497152&r2=1497153&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt (original)
+++ maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt Wed Jun 26 23:05:44 2013
@@ -162,7 +162,7 @@ I will promote the artifacts to the cent
 
   The official Apache release is the 'source-release' bundle. All releases must be copied to {{{http://www.apache.org/dist/maven/}the official 
   release area}}. The release area is maintained with svnsubpub. To deliver a release, you add it to 
-  {{{https://dist.apache.org/repos/dist/release/maven}the subversion repository for the dist area}.
+  {{{https://dist.apache.org/repos/dist/release/maven}the subversion repository for the dist area}}.
 
   The Maven dist area is {{{https://dist.apache.org/repos/dist/release/maven}}}. In here, you will
   find a series of subdirectories (plugins, scm, etc.) Add the release, its signature, and corresponding
@@ -285,4 +285,4 @@ Enjoy,
  This might also be a step to take if other shared resources are released, or if plugin releases are
  of particular interest to that group.
 
- [[7]] Celebrate :o)
\ No newline at end of file
+ [[7]] Celebrate :o)