aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lu <chrislusf@users.noreply.github.com>2020-12-29 21:15:09 -0800
committerGitHub <noreply@github.com>2020-12-29 21:15:09 -0800
commitadda3207c4d98532b6666d7da7a4dccdc26090be (patch)
tree0393a01ce39d582686a42cc180fc3420e6f33468
parentc1cd6dd8d69c14d8048a409cc352e071b5821a3c (diff)
downloadseaweedfs-adda3207c4d98532b6666d7da7a4dccdc26090be.tar.xz
seaweedfs-adda3207c4d98532b6666d7da7a4dccdc26090be.zip
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 70e2ba0b2..f705e4ad7 100644
--- a/README.md
+++ b/README.md
@@ -335,7 +335,7 @@ Usually hot data are fresh and warm data are old. SeaweedFS puts the newly creat
With the O(1) access time, the network latency cost is kept at minimum.
-If the hot~warm data is split as 20~80, with 20 servers, you can achieve storage capacity of 100 servers. That's a cost saving of 80%! Or you can repurpose the 80 servers to store new data also, and get 5X storage throughput.
+If the hot/warm data is split as 20/80, with 20 servers, you can achieve storage capacity of 100 servers. That's a cost saving of 80%! Or you can repurpose the 80 servers to store new data also, and get 5X storage throughput.
[Back to TOC](#table-of-contents)