From d899df15a7ea24e46220c5b6c9ca59cd825dd3e9 Mon Sep 17 00:00:00 2001 From: ankur22 Date: Wed, 5 Jun 2024 11:11:03 +0100 Subject: [PATCH] Update promise chaining wording --- docs/sources/v0.51.x/using-k6-browser/migrating-to-k6-v0-52.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/v0.51.x/using-k6-browser/migrating-to-k6-v0-52.md b/docs/sources/v0.51.x/using-k6-browser/migrating-to-k6-v0-52.md index ce3f9bc020..b56ed0379f 100644 --- a/docs/sources/v0.51.x/using-k6-browser/migrating-to-k6-v0-52.md +++ b/docs/sources/v0.51.x/using-k6-browser/migrating-to-k6-v0-52.md @@ -305,7 +305,7 @@ export default async function () { ### Promise chaining in v0.51 -No. If you want to chain promises with the APIs soon to be migrated over to async, you won't be able to do that until after the migration and release of k6 `v0.52`. +This won't work. If you want to chain promises with the APIs soon to be migrated over to async, you won't be able to do that until after the migration and release of k6 `v0.52`. For example, you can't do this yet: