From 02c2978e046bb29b0425210bb92cfd673e3197a0 Mon Sep 17 00:00:00 2001 From: Semen Date: Wed, 28 Feb 2024 04:21:45 +0200 Subject: [PATCH] docs: remove excess quotes in Restricted parameters object (#2474) Co-authored-by: Akshat Nema <76521428+akshatnema@users.noreply.github.com>%0ACo-authored-by: Quetzalli %0ACo-authored-by: Ansh Goyal --- pages/docs/migration/migrating-to-v3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/migration/migrating-to-v3.md b/pages/docs/migration/migrating-to-v3.md index 73f48d79494..84fa545b8e1 100644 --- a/pages/docs/migration/migrating-to-v3.md +++ b/pages/docs/migration/migrating-to-v3.md @@ -409,7 +409,7 @@ Parameters have often prioritized convenience over accurately reflecting real-wo In v2, we significantly streamlined the Schema Object. While the previous version offered full capability with numerous, often underutilized options, it posed challenges in serializing objects or booleans in the channel path. -The new v3 simplifies this by consistently using the string type and limiting available properties. Now, you can only access `enum`, `default`, `description`, `examples`, and `location`, ensuring a more focused and practical approach." +The new v3 simplifies this by consistently using the string type and limiting available properties. Now, you can only access `enum`, `default`, `description`, `examples`, and `location`, ensuring a more focused and practical approach. ```yml asyncapi: 2.6.0