Skip to content

Commit c57f9b2

Browse files
committed
more typos
1 parent fa5e0b3 commit c57f9b2

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

contents/tutorials/nuxtjs-ab-tests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,7 @@ const captureEventInPostHog = () => {
261261

262262
Now, when you refresh the page, the button text is already set when the page loads.
263263

264-
> **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.
264+
> **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.
265265
>
266266
> The solution to this is to [`identify`](/docs/product-analytics/identify) your users using a distinct ID which is not cookie-based.
267267

contents/tutorials/one-time-feature-flags.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ tags:
1111

1212
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.
1313

14-
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.
14+
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.
1515

1616
## Creating our Express app
1717

0 commit comments

Comments
 (0)