svn commit: r1818083 - /subversion/site/staging/docs/release-notes/1.3.html

[lu...@apache.org]

Author: luke1410
Date: Wed Dec 13 23:53:29 2017
New Revision: 1818083

URL: http://svn.apache.org/viewvc?rev=1818083&view=rev
Log:
* site/staging/docs/release-notes/1.3.html: JavaSVN is now known as SVNKit so
  update the link and adjust the wording.

Credits to: jcorvel

Modified:
    subversion/site/staging/docs/release-notes/1.3.html

Modified: subversion/site/staging/docs/release-notes/1.3.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.3.html?rev=1818083&r1=1818082&r2=1818083&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.3.html (original)
+++ subversion/site/staging/docs/release-notes/1.3.html Wed Dec 13 23:53:29 2017
@@ -434,9 +434,9 @@ working, even with older clients.</p>
 
 <p>However, programs that interact with the working copy property
 files without using the official Subversion APIs or binaries may
-experience problems.  JavaSVN (previously available under
-http://tmate.org/svn/) is the only project that we know of that falls
-into this category, and they have been notified accordingly.  If you
+experience problems.  JavaSVN (now known as
+<a href="https://svnkit.com/">SVNKit</a>) is the only project that we know of
+that falls into this category, and they have been notified accordingly.  If you
 happen to be using or developing software that, similarly, bypasses the
 Subversion APIs, then you may need to make a minor alteration to the
 parsing routines. See <a href="https://svn.apache.org/r856929"