summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Dover <zac.dover@proton.me>2023-09-10 18:31:30 +0200
committerZac Dover <zac.dover@proton.me>2023-09-10 18:38:26 +0200
commit436fbf7a3e0960ebb51a0dc66d9c1d405bf6875f (patch)
treece6fc4a8743f1032e56d4d7cd129c25c83c6bd9f
parentMerge pull request #53353 from zdover23/wip-doc-2023-09-10-architecture-1-of-x (diff)
downloadceph-436fbf7a3e0960ebb51a0dc66d9c1d405bf6875f.tar.xz
ceph-436fbf7a3e0960ebb51a0dc66d9c1d405bf6875f.zip
doc/architecture.rst - edit a sentence
Change the sentence structure of a sentence because the verb "experience" looked like the abstract noun "experience" when I read it with fresh eyes. I chose the perhaps TESOL-unfriendly verb "incur", but I believe it is right. Signed-off-by: Zac Dover <zac.dover@proton.me>
-rw-r--r--doc/architecture.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/architecture.rst b/doc/architecture.rst
index 12ebacad5a0..7c8c9d03726 100644
--- a/doc/architecture.rst
+++ b/doc/architecture.rst
@@ -100,10 +100,9 @@ Scalability and High Availability
In traditional architectures, clients talk to a centralized component. This
centralized component might be a gateway, a broker, an API, or a facade. A
centralized component of this kind acts as a single point of entry to a complex
-subsystem. Architectures that rely upon this kind of centralized component
-experience limits to performance and scalability and have a single point of
-failure. If the centralized component goes down, the whole system becomes
-unavailable.
+subsystem. Architectures that rely upon such a centralized component have a
+single point of failure and incur limits to performance and scalability. If
+the centralized component goes down, the whole system becomes unavailable.
Ceph eliminates this centralized component. This enables clients to interact
with Ceph OSDs directly. Ceph OSDs create object replicas on other Ceph Nodes