summaryrefslogtreecommitdiff
path: root/src/content/en/blog
diff options
context:
space:
mode:
Diffstat (limited to 'src/content/en/blog')
-rw-r--r--src/content/en/blog/2020/10/19/feature-flags.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/content/en/blog/2020/10/19/feature-flags.adoc b/src/content/en/blog/2020/10/19/feature-flags.adoc
index 8788407..5e08650 100644
--- a/src/content/en/blog/2020/10/19/feature-flags.adoc
+++ b/src/content/en/blog/2020/10/19/feature-flags.adoc
@@ -108,7 +108,7 @@ how long the transition will last.
On the *frontend* you have less control: even though you can choose to make a
new version available any time you wish, you can't
-force{empy}footnote:force[
+force{empty}footnote:force[
Technically you could force a reload with JavaScript using
`window.location.reload()`, but that not only is invasive and impolite, but
also gives you the illusion that you have control over the client when you
@@ -143,7 +143,7 @@ worth it.
:kubernetes-deployment: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-a-deployment
:play-store-rollout: https://support.google.com/googleplay/android-developer/answer/6346149?hl=en
-:app-store-rolllout: https://help.apple.com/app-store-connect/#/dev3d65fcee1
+:app-store-rollout: https://help.apple.com/app-store-connect/#/dev3d65fcee1
A rollout is used to _roll out_ a new version of software.