diff --git a/docs/runtime/sync.md b/docs/runtime/sync.md
index 16ddcfda0a0f6e84d51d70719ca2349e975cce65..305e02ae0f4a03f02538f64303e52c99c6b2dfa6 100644
--- a/docs/runtime/sync.md
+++ b/docs/runtime/sync.md
@@ -200,4 +200,4 @@ Suppose a synchronous region is (partially) established, and the component `E` e
 
 So that is to say that this `ClosePort(sync)` causes instant failure of `C` if it has used the closed port in a round without consensus, or if it uses that port in the future. Note that this `ClosePort(sync)` system causes cascading failures throughout the disjoint synchronous regions. This is as intended: once one component's PDL program can no longer be executed, we cannot depend on the discovery of all the peers that constitute the intended synchronous region. So instead we rely on a peer-to-peer mechanism to make sure that every component is notified of failure.
 
-However, while these cascading peer-to-peer `ClosePort(sync)` messages are happily shared around, we still have a leader component somewhere, and components that have not yet been notified of the failure. Here we can make several design choices to 
\ No newline at end of file
+However, while these cascading peer-to-peer `ClosePort(sync)` messages are happily shared around, we still have a leader component somewhere, and components that have not yet been notified of the failure.
\ No newline at end of file