fix(typescript): typo

libs/website/ui-typescript/src/lib/benchmark.tsx

@@ -70,11 +70,11 @@ export function Benchmark(): React.JSX.Element {
         <div className="mx-auto max-w-2xl">
           <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
             What's worth pointing out here is the difference in time when
-            dealing with incremental updates. With Path Aliases, TypeScript need
-            to perform full rebuild of every package. However, with project
-            references in place, TypeScript can understand what packages have
-            changed and skip a rebuild if possible, reducing the time needed to
-            rebuild.
+            dealing with incremental updates. With Path Aliases, TypeScript
+            needs to perform full rebuild of every package. However, with
+            project references in place, TypeScript can understand what packages
+            have changed and skip a rebuild if possible, reducing the time
+            needed to rebuild.
           </p>
         </div>
       </article>

libs/website/ui-typescript/src/lib/prebuild-callout.tsx

@@ -37,7 +37,7 @@ export function PrebuildCallout(): React.JSX.Element {
             </p>
             <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
               If the modules in your monorepo are for internal use and will
-              never be published to a package registry, this is valid option.
+              never be published to a package registry, this is a valid option.
             </p>
           </div>
 
@@ -59,13 +59,13 @@ export function PrebuildCallout(): React.JSX.Element {
             </h2>
             <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
               With prebuilding, you're running the build tasks needed for any
-              module in the monorepo ahead of time. Your export the compiled and
+              module in the monorepo ahead of time. You export the compiled and
               generated code, and provide the generated types.
             </p>
             <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
               The benefit here is that everything can be done ahead of time, so
               you only have one task being run. However, if you need to change
-              of the modules being consumed, you need to rerun the build for the
+              the modules being consumed, you need to rerun the build for the
               affected module. Some monorepo tools, like{' '}
               <a href="https://nx.dev">Nx</a> provide a way to do this, but
               other tools might not.
@@ -89,7 +89,7 @@ export function PrebuildCallout(): React.JSX.Element {
         <div className="mx-auto max-w-2xl">
           <p className="mt-3 text-xl text-gray-700 sm:mt-4 dark:text-gray-300">
             Either option can work, the major factor would be if you are
-            publishing the libraries for others to use outside of your monorpeo.
+            publishing the libraries for others to use outside of your monorepo.
           </p>
         </div>
       </article>

libs/website/ui-typescript/src/lib/project-structure.tsx

@@ -42,7 +42,7 @@ export function ProjectStructure(): JSX.Element {
               .
             </h2>
             <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
-              By know how each of these concepts work in regards to you
+              By knowing how each of these concepts works in regards to you
               TypeScript monorepo, you can better organize your codebase and
               keep your builds fast.
             </p>

libs/website/ui-typescript/src/lib/type-references.tsx

@@ -19,7 +19,7 @@ export function TypeReferences(): React.JSX.Element {
           </a>
         </div>
         <p className="mx-auto mt-4 max-w-3xl text-center text-xl text-gray-700 dark:text-gray-300">
-          Provide deeper understanding of your monorepos types and speed up
+          Provide deeper understanding of your monorepo's types and speed up
           TypeScript compilation for large projects.
         </p>
       </div>
@@ -57,7 +57,7 @@ export function TypeReferences(): React.JSX.Element {
               can better optimize how it returns any type information for your
               editor. In addition to the type benefits, TypeScript can now
               compile pieces of your codebase in better isolation. In the
-              loosest sense, project references turns the TypeScript compiler
+              loosest sense, project references turn the TypeScript compiler
               into a monorepo tool.
             </p>
           </div>
@@ -79,12 +79,12 @@ export function TypeReferences(): React.JSX.Element {
         <div className="mx-auto max-w-2xl">
           <p className="mt-3 text-lg text-gray-700 dark:text-gray-300">
             Project references can have some draw back in monorepos that include
-            a lot of types. For instance, trcp can generate type information for
+            a lot of types. For instance, trpc can generate type information for
             every route in your API. Normally this is great, and project
             references can make sure that type information is available to you.
             But if you have a large API, you could be dealing with significant
             delays in your editor when you try to trigger auto-completion or get
-            a symbols type. This isn't only isolated to trpc, but any monorepo
+            a symbol's type. This isn't only isolated to trpc, but any monorepo
             that has a large and complex type setup.
           </p>
         </div>