diff --git a/contents/tutorials/nuxtjs-ab-tests.md b/contents/tutorials/nuxtjs-ab-tests.md
index 06f5433c9edc..e217b8f24015 100644
--- a/contents/tutorials/nuxtjs-ab-tests.md
+++ b/contents/tutorials/nuxtjs-ab-tests.md
@@ -261,7 +261,7 @@ const captureEventInPostHog = () => {
 
 Now, when you refresh the page, the button text is already set when the page loads. 
 
-> **Note:** This only works on subsequence visits to your app where the PostHog cookie is set. Using this method still requires waiting for PostHog and feature flags to load on the first visit.
+> **Note:** This only works on subsequent visits to your app where the PostHog cookie is set. Using this method still requires waiting for PostHog and feature flags to load on the first visit.
 > 
 > The solution to this is to [`identify`](/docs/product-analytics/identify) your users using a distinct ID which is not cookie-based.
 
diff --git a/contents/tutorials/one-time-feature-flags.md b/contents/tutorials/one-time-feature-flags.md
index ce10171d28ab..757fa147016e 100644
--- a/contents/tutorials/one-time-feature-flags.md
+++ b/contents/tutorials/one-time-feature-flags.md
@@ -11,7 +11,7 @@ tags:
 
 Sometimes you want to show users a component or some content only once. You can use a field in their user model or store it locally, but this gets messy fast. It also might prevent you from changing it remotely. A better way to do this is a feature flag that changes once a user completes what you want.
 
-In this tutorial, we show how to set up a one-time feature flag using PostHog by building a basic Express.js API that provides one response on the first request, and a different one on subsequence requests.
+In this tutorial, we show how to set up a one-time feature flag using PostHog by building a basic Express.js API that provides one response on the first request, and a different one on subsequent requests.
 
 ## Creating our Express app