From db00d19d7f50970ff69e2dbe7f3698e362eaf042 Mon Sep 17 00:00:00 2001 From: Bruno Carlin Date: Mon, 16 Jun 2025 02:58:41 +0200 Subject: [PATCH] fix: typos --- content/blog/007-prepare-for-the-next-internet-outage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/blog/007-prepare-for-the-next-internet-outage.md b/content/blog/007-prepare-for-the-next-internet-outage.md index 83f7249..e2e5df0 100644 --- a/content/blog/007-prepare-for-the-next-internet-outage.md +++ b/content/blog/007-prepare-for-the-next-internet-outage.md @@ -49,8 +49,8 @@ least one of these vendors. product? Is your app deployed with a Github Action ? The more you know, the more you’re prepared. * *Vendor Due Diligence*: Uptime guarantees (3? 4? 5 nines?) are just marketing. - Take it as such. What is your vendor’s architecture? its Continuity plan? Its - transparency on incidents? those are far more important criteria. + Take it as such. What is your vendor’s architecture? Its continuity plan? Its + transparency on incidents? Those are far more important criteria. * *Consider Multi-Cloud Strategies*: You would not put all your servers in the same datacenter? Then do not put all your infrastructure in the same IaaS provider! (If you would, you should do something about it!) @@ -112,7 +112,7 @@ some that will affect your business. Be prepared: * Know your infrastructure, your vendors, their vendors, etc. -* Asses risks on a regular basis. Your app evolves, your vendors too. What is +* Assess risks on a regular basis. Your app evolves, your vendors too. What is true at one moment is not at the next. * Plan for the worst case. Incidents will happen. Your job is to make it so that the user experience is not impacted.