From 82daea9151069664c858bdcba4ff5420e2b5c672 Mon Sep 17 00:00:00 2001 From: Shankar A M Date: Thu, 16 Oct 2025 16:18:22 +0530 Subject: [PATCH] Update best-practice.mdx --- help/best-practice.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/help/best-practice.mdx b/help/best-practice.mdx index 5796380..9ffef02 100644 --- a/help/best-practice.mdx +++ b/help/best-practice.mdx @@ -22,7 +22,7 @@ icon: "lightbulb" Start with some small issues in your backlog to get some quick results and learn how cto.new works. - You'll son get used to working with [cto.new](http://cto.new) and planning bigger tasks. + You'll soon get used to working with [cto.new](http://cto.new) and planning bigger tasks. We recommend that you review cto.new's code before merging it. This not only helps ensure it is correct, but keeps you in the loop on your own codebase. @@ -53,4 +53,4 @@ Let cto.new know what your testing requirements are for a particular task, or an **Avoid vague tasks** -cto.new will attempt to complete vague or poorly defined tasks, but the outcome is unlikely to be what you had in mind. \ No newline at end of file +cto.new will attempt to complete vague or poorly defined tasks, but the outcome is unlikely to be what you had in mind.