Skip to content

Scheduling infrastructure for absolutely everyone.

chore(docs): update 'Calendso' to 'Cal.com' in documentation (#21661)

nav34beadeef65d
diff --git a/docs/developing/open-source-contribution/code-styling.mdx b/docs/developing/open-source-contribution/code-styling.mdx
index 8882970ed32..25200b13eb0 100644
--- a/docs/developing/open-source-contribution/code-styling.mdx
+++ b/docs/developing/open-source-contribution/code-styling.mdx
@@ -10,11 +10,11 @@ We use a number of style guides written by other amazing companies, simply becau
We don't expect you to study every single rule of each style guide, but these are great reference points as to how your code should be styled. We may reject a pull request if your code style significantly differs from these style guides however.
### ESLint & Prettier
-Calendso uses the ESLint and Prettier formatting tools, and the repository comes with defined rules for each tool. We recommend setting up both tools and using these to help automatically style your code to our guidelines.
+Cal.com uses the ESLint and Prettier formatting tools, and the repository comes with defined rules for each tool. We recommend setting up both tools and using these to help automatically style your code to our guidelines.
### JavaScript/TypeScript
-We use the
+We use the
for all JavaScript and Typescript code.
### HTML & CSS
-We use the [Google HTML/CSS Style Guide](https://google.github.io/styleguide/htmlcssguide.html) for any HTML and CSS markup. However, exceptions to the HTML guide apply where JSX differentiates from standard HTML.
\ No newline at end of file
+We use the [Google HTML/CSS Style Guide](https://google.github.io/styleguide/htmlcssguide.html) for any HTML and CSS markup. However, exceptions to the HTML guide apply where JSX differentiates from standard HTML.