aboutsummaryrefslogtreecommitdiff
path: root/progress/Network.tex
diff options
context:
space:
mode:
authorHolden Rohrer <holden.rohrer@gmail.com>2019-10-21 23:06:41 -0400
committerHolden Rohrer <holden.rohrer@gmail.com>2019-10-21 23:11:16 -0400
commit80b5bddbf692209973dad6b81343be35105afd31 (patch)
tree4ae214adbfaba8e6ebe25b75b417b6c546677059 /progress/Network.tex
parenta944792dbecf1ed92af4ce413a6879891780e4d5 (diff)
removed words
Diffstat (limited to 'progress/Network.tex')
-rw-r--r--progress/Network.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/progress/Network.tex b/progress/Network.tex
index 700189e..0bf84d2 100644
--- a/progress/Network.tex
+++ b/progress/Network.tex
@@ -1,4 +1,4 @@
-Network connectivity is usually an issue on a local scale: one router or modem or device has a broken component---usually software that needs to be reset in one way or another. However, it rears its head on a very large scale as well: routing connections, as mentioned earlier, relies on the ability to communicate with at least one ``neighbor'' on the network, which is fine unless that neighbor goes down for whatever reason. And in non-decentralized systems, such as modern ISPs, that's exactly what happens: a software bug or power outage or any sort of problem tanks an entire area's coverage for hours to days.
+Network connectivity is often an issue on a local scale: one router or modem or device breaks. However, on a : routing connections, as mentioned earlier, rely on the ability to communicate with at least one ``neighbor'' on the network, which is fine until that neighbor goes down. And in centralized systems, such as commercial ISPs', that's exactly what happens: any sort of problem can tank an entire area's coverage for hours to days.
\sinclude Combinatorics Applications:net-apps