Skip to content

Commit 03354b4

Browse files
committed
Fix typos.
1 parent daeb6b5 commit 03354b4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/tutorials/migrating-webhooks-to-svix.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,17 @@ To achieve this cut-over, you would want to locate the centralized location wher
1414

1515
Once located, you would want to change these to conditionally send webhooks to either your existing legacy system or Svix. The condition can use feature flags, a property on the target customer, a hardcoded list of customers, or whatever other mechanism you want to use to toggle which customers should use which system.
1616

17-
The next step is to copy over the data from your existing legacy system to Svix. You can do it using the Svix API as demonstrated [in the quickstart document](../quickstart.mdx). Namely, you'd want to [create a a Svix application](https://api.svix.com/docs#tag/Application/operation/v1.application.create) for each of your customers, and [creating the relevant endpoints](https://api.svix.com/docs#tag/Endpoint/operation/v1.endpoint.create) for each application.
17+
The next step is to copy over the data from your existing legacy system to Svix. You can do it using the Svix API as demonstrated [in the quickstart document](../quickstart.mdx). Namely, you'd want to [create a Svix application](https://api.svix.com/docs#tag/Application/operation/v1.application.create) for each of your customers, and [create the relevant endpoints](https://api.svix.com/docs#tag/Endpoint/operation/v1.endpoint.create) for each application.
1818

19-
It easiest to start by cutting over traffic only for test accounts, or accounts of will beta testers to make sure everything works as expected.
19+
It's easiest to start by cutting over traffic only for test accounts, or those of beta testers to make sure everything works as expected.
2020

2121
Once you see everything works, you can gradually toggle the rest of your customers to use Svix instead of the old system. Once done, you can bring down the old system and remove the code that calls it and the associated conditionals.
2222

2323
That's it! You can now safely delete all the thousands of lines of code and all of the infrastructure of your old systems. The transition is now complete!
2424

25-
Most of our customers gradually move over their customers over the span of a day or two. Though you can go as slow or fast as you're comfortable is.
25+
Most of our customers gradually move over their customers over the span of a day or two. Though you can go as slow or fast as you're comfortable.
2626

27-
We help a lot of customers switch from their legacy home-grown systems to Svix, so please reach out it you have any questions. The team will be happy to help!
27+
We help a lot of customers switch from their legacy home-grown systems to Svix, so please reach out if you have any questions. The team will be happy to help!
2828

2929
## Additional considerations
3030

0 commit comments

Comments
 (0)