svn commit: r1599788 - /phoenix/site/source/src/site/markdown/index.md

[gr...@apache.org]

Author: greid
Date: Tue Jun  3 20:40:32 2014
New Revision: 1599788

URL: http://svn.apache.org/r1599788
Log:
PHOENIX-1014 Fix broken link to performance page

Modified:
    phoenix/site/source/src/site/markdown/index.md

Modified: phoenix/site/source/src/site/markdown/index.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/index.md?rev=1599788&r1=1599787&r2=1599788&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/index.md (original)
+++ phoenix/site/source/src/site/markdown/index.md Tue Jun  3 20:40:32 2014
@@ -40,7 +40,7 @@ A Phoenix table is created through the [
 All schema is versioned, and prior versions are stored forever. Thus, snapshot queries over older data will pick up and use the correct schema for each row.
 
 ####Salting
-A table could also be declared as salted to prevent HBase region hot spotting. You just need to declare how many salt buckets your table has, and Phoenix will transparently manage the salting for you. You'll find more detail on this feature [here](salted.html), along with a nice comparison on write throughput between salted and unsalted tables [here](performance.htm#salting).
+A table could also be declared as salted to prevent HBase region hot spotting. You just need to declare how many salt buckets your table has, and Phoenix will transparently manage the salting for you. You'll find more detail on this feature [here](salted.html), along with a nice comparison on write throughput between salted and unsalted tables [here](performance.html#salting).
 
 ####Schema at Read-time
 Another schema-related feature allows columns to be defined dynamically at query time. This is useful in situations where you don't know in advance all of the columns at create time. You'll find more details on this feature [here](dynamic_columns.html).