Updated tagline

Author: CharlieDigital

docs/.vitepress/config.mts

@@ -3,7 +3,7 @@ import { defineConfig } from 'vitepress'
 // https://vitepress.dev/reference/site-config
 export default defineConfig({
   title: "TypeScript is Like C#",
-  description: "Outgrowing Node.js? If you already know TypeScript, then learning C# is easy!  This guide walks you through the similarities (and differences) between TypeScript and C#",
+  description: "A guide for backend devs. If you already know TypeScript, then learning C# is easy!  This guide walks you through the similarities (and differences) between TypeScript and C#",
   sitemap: {
     hostname: 'https://typescript-is-like-csharp.chrlschn.dev'
   },

docs/index.md

@@ -4,7 +4,7 @@ layout: home
 
 hero:
   name: "TypeScript is Like C#"
-  text: "Outgrowing Node.js?"
+  text: "A Backend Guide"
   image:
     src: /csharp-logo.png
     alt: C# logo
@@ -18,7 +18,7 @@ hero:
       link: /pages/basics/variables
     - theme: alt
       text: Let's Deep Dive!
-      link: /pages/intermediate/nest-vs-controller-api
+      link: /pages/intermediate/databases-and-orms
 
 features:
   - title: Easy to Learn

docs/pages/intermediate/databases-and-orms.md

@@ -617,7 +617,7 @@ var loadedRunners = await db.Runners
   </template>
 </CodeSplitter>
 
-I've taken some liberal formatting here to help make the Prisma query more readable, but you can see that as the query gets larger, it is actually quite difficult to manage and refactor while the EF query remains quite legible and easy to understand.  .NET has first-class expression trees that can be evaluated at runtime to produce the queries whereas on the Prisma side, the code is effectively *building and expression tree*.
+I've taken some liberal formatting here to help make the Prisma query more readable (Prettier would make this code even more lines!), but you can see that as the query gets larger, it is actually quite difficult to manage and refactor while the EF query remains quite legible and easy to understand.  .NET has first-class expression trees that can be evaluated at runtime to produce the queries whereas on the Prisma side, the code is effectively *building and expression tree*.
 
 With Prisma, a better strategy might be to use Prisma on the write side and [Kysely](https://kysely.dev/) on the read side much like how some teams with C# might use Entity Framework on the write side and [Dapper](https://github.com/DapperLib/Dapper) on the read side for more complex queries (though Entity Framework's threshold for complex read queries is higher than Prisma's).
 
@@ -709,7 +709,7 @@ See [**the unit tests in the repo**](https://github.com/CharlieDigital/typescrip
 <CodeSplitter>
   <template #left>
 
-```ts{43,52,55-60}
+```ts{43,53,56-61}
 // 📄 results-repository.ts: Sample repository
 @Injectable()
 export class ResultsRepository {