aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXe Iaso <me@christine.website>2022-05-15 08:00:07 -0400
committerXe Iaso <me@christine.website>2022-05-18 16:44:55 -0400
commit62dc15c33937264402c150d85b155d836644b4d1 (patch)
tree6229a75dc1d14e63b4de1c3043178d97e450f63e
parent2432b5a4fc6bc068b5d5b8841deedcfd2e9f5dd5 (diff)
downloadxesite-62dc15c33937264402c150d85b155d836644b4d1.tar.xz
xesite-62dc15c33937264402c150d85b155d836644b4d1.zip
infrastructure
Signed-off-by: Xe Iaso <me@christine.website>
-rw-r--r--blog/fly.io-heroku-replacement.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/blog/fly.io-heroku-replacement.markdown b/blog/fly.io-heroku-replacement.markdown
index eba9208..7a502a4 100644
--- a/blog/fly.io-heroku-replacement.markdown
+++ b/blog/fly.io-heroku-replacement.markdown
@@ -67,7 +67,7 @@ generational leap in the capabilities of what a Platform as a Service can do.
Even more critical is that every app gets its own static IP address that you can
use for IP based firewall rules. This is something that was straight up
impossible in Heroku due to Heroku being a reseller of AWS, but since fly.io
-owns their own infreastructure and IP space, they can do this with ease. Your
+owns their own infrastructure and IP space, they can do this with ease. Your
applications can be reached on a predictable IP and they will have outgoing
connections with the same IP.