Skip to content

Update best-practice.mdx #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update best-practice.mdx #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions help/best-practice.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
</Accordion>
<Accordion title="Review cto.new's code" icon="face-monocle">
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.
Expand Down Expand Up @@ -53,4 +53,4 @@ Let cto.new know what your testing requirements are for a particular task, or an

<Icon icon="question" size={18} /> **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.
cto.new will attempt to complete vague or poorly defined tasks, but the outcome is unlikely to be what you had in mind.