Update addition titles

Author: joan

a-new-trend-for-databases.mdx

@@ -1,6 +1,6 @@
 ---
 title: "A new trend for databases: platforms"
-description: "It's about more than the data stored in your table. It's what you can do with that data."
+description: "It's about more than the data stored in your table; it's what you can do with that data."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/database-platforms-trend.png
   alt: Data platforms

auth-js.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Xata and Auth․js on two Next․js apps: app directory and pages directory"
-description: "Let's build Next.js apps with JWT authentication, Auth.js, and Xata."
+title: "Build Next.js apps with JWT authentication, Auth.js, and Xata"
+description: "Use Xata and Auth․js on two Next․js apps: app directory and pages directory"
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/xata-authjs-nextjs.png
   alt: Xata and ChatGPT logos
@@ -19,7 +19,7 @@ Working the conditions and conventions of each directory can get you with any ro
 
 Before going into the Next.js specifics, let's first understand our goals with this project. Visualizing the mental model is an important step to ensure your user's data is switching hands as little as possible.
 
-## Defining a Mental Model
+## Defining a mental model
 
 A diagram is probably the fastest way to visualizing a process. This is important to see if there aren't any redundant calls, or if any of those requests are chained in some condition. Chained requests are the grim reapers of perceived performance, we need to get those out of the way as soon as possible.
 
@@ -249,7 +249,7 @@ Finally, all code is in place to:
 
 What we need now is a set of keys to effectively connect to those services in a secure way.
 
-## Setup Environment Variables
+## Configure environment variables
 
 The environment variables `GITHUB_ID` and `GITHUB_SECRET` are provided by GitHub once you register an [OAuth App](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app). For your code to run properly you will need to have a `.env` (or `.env.local`) file looking like:
 
@@ -269,7 +269,7 @@ NEXTAUTH_SECRET=<a random secret string>
 
 Finally, it's time to manage some data.
 
-## Fetching User Data
+## Fetching user data
 
 There are a few ways with which you can provide secure access to routes in your Auth.js app. One is via the Auth.js middleware, this will redirect anyone without a `session` automatically to the login route you set up. This approach should work in both App Directory and Pages Directory.
 
@@ -279,7 +279,7 @@ Lastly, in the app directory, the best way is to use `getServerSession` method,
 
 When working with React Server components, don't worry about firing multiple requests, it always hit the same endpoint and therefore Next.js will be able to deduplicate it, so there will only be one fetch request.
 
-## Accessing User Specific Data
+## Accessing user specific data
 
 Once we got Auth setup, we can treat Row-Level Security (RLS) as an if/else statement. For example, take this contrived profile page:
 
@@ -306,7 +306,7 @@ export const getServerSideProps = async ({
 }
 ```
 
-In the above example, we are using the user's email as their unique identifier (or Primary Key). And we implemented a getter in a file named `db.server.ts`. Let's see how that looks like using the Xata SDK.
+In the above example, we are using the user's email as their unique identifier (or primary key). And we implemented a getter in a file named `db.server.ts`. Let's see how that looks like using the Xata SDK.
 
 ```tsx
 // the file generated via our CLI
@@ -358,7 +358,7 @@ export const fetchData = async (userEmail: string) => {
 };
 ```
 
-## Working Code
+## Working code
 
 Now that we are done, you can compare your code or check the components that we wrote to use this logic in our examples repository:
 

branching-benefits-git-databases.mdx

@@ -1,6 +1,6 @@
 ---
-title: "How branching brings predictability to web development"
-description: "Let's explore the benefits of branching in developer workflows, and how Xata brings these benefits to data infrastructure."
+title: "Branching brings predictability to web development"
+description: "Explore the advantages of branching in developer workflows and how Xata brings these benefits to data infrastructure."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/branching-benefits-git-databases.png
   alt: Xata
@@ -26,7 +26,7 @@ Unlike tree branches, though, Git branches are capable of merging with another b
 
 ![Merging Feature Branches into a Main Branch in Git](https://c-v.sh/unforgeddiddlers.png)
 
-### Branching & Pull Requests
+### Branching and pull requests
 
 Another Git feature that goes hand-in-hand with branching to enhance the predictability of the development process is _pull requests_. It's especially powerful today because of how some tools in the Git ecosystem—like [GitHub](https://github.com/), [Bitbucket](https://bitbucket.org/product), and [GitLab](https://about.gitlab.com/)—have built additional functionality around pull requests to promote better collaboration among developers and continuous integration.
 
@@ -36,7 +36,7 @@ You can use PRs to not only review the code that is being pushed to the main bra
 
 [Vercel](https://vercel.com/)'s [deploy preview](https://vercel.com/features/previews) feature is one of the latest tools that takes advantage of the branching and pull request mechanisms to extend the predictability Git offers beyond the code level.
 
-### Deployment Previews with Vercel
+### Deployment previews with Vercel
 
 Vercel allows deploying websites directly from a Git repository hosted on GitHub, GitLab, or Bitbucket. Once you declare the repository's production branch, every time you commit changes to it through merging pull requests, Vercel automatically rebuilds and deploys the website to its platform.
 

bulletproof-docs-links.mdx

@@ -1,6 +1,6 @@
 ---
 title: "A journey to bulletproof links in documentation"
-description: "How we permanently fixed the problem of broken internal links in our documentation."
+description: "Learn how we solved the issue of broken internal links in our documentation, once and for all."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/bulletproof-docs-links.png
   alt: Xata
@@ -29,9 +29,9 @@ So far, we had no way to make sure that links between pages were working and tha
   position="center"
 />
 
-This is fine, we all make mistakes, but let’s learn from this together!
+This is fine! We all make mistakes, but let’s learn from this together!
 
-## The Plan
+## The plan
 
 The first step is to list our requirements so we have our goal well defined. We want quick feedback if something gets broken, so we can fix it before merging to production. For that, we need to be able to run the docs consistently in different environments:
 
@@ -151,7 +151,7 @@ and another [link](/rest-api/delete)
 
 That’s essentially all we need for a proof of concept (POC), we are now more confident that we should be able to extract every link from our documentation. Let’s try with some real data!
 
-## The Real Deal
+## The real deal
 
 First, we need a way to load all our Markdown files. Luckily, [npm](https://www.notion.so/A-Journey-to-Bulletproof-Links-in-Documentation-f108c0ed0acd464bb1e6310519d19e37) already has a solution for us. 😀
 
@@ -203,7 +203,7 @@ And… it works! Not useful yet, but we are going in the right direction!
   position="center"
 />
 
-This is also a nice opportunity for us to see what links we actually have! And we can already spot some patterns that we need to deal with as external links (example: [`https://stackoverflow.com/questions/4423061/how-can-i-view-http-headers-in-google-chrome`](https://stackoverflow.com/questions/4423061/how-can-i-view-http-headers-in-google-chrome)) and links with anchors (example: `/cli/getting-started#code-generation`)
+This is also a nice opportunity for us to see what links we actually have! We can already spot some patterns that we need to deal with as external links (example: [`https://stackoverflow.com/questions/4423061/how-can-i-view-http-headers-in-google-chrome`](https://stackoverflow.com/questions/4423061/how-can-i-view-http-headers-in-google-chrome)) and links with anchors (example: `/cli/getting-started#code-generation`)
 
 First, let’s exclude external links, they are out of our scope since we’re not interested in _other people’s 404s._ We may add this later since we don’t want to link to broken content in the longer term, but for now **scope hammering keeps us focused**.
 
@@ -447,7 +447,7 @@ await unified()
   });
 ```
 
-## The Wrap Up
+## The wrap-up
 
 This is the final version (the one used in our actual documentation repository!)
 

chatgpt-on-your-data.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Xata & OpenAI: ChatGPT for your data"
-description: Xata now lets you ask your data questions.
+description: Use Xata to you ask your data questions.
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/chatgpt-on-your-data.png
   alt: Xata and ChatGPT logos

data-modeling-in-typescript.mdx

@@ -1,6 +1,6 @@
 ---
 title: "The importance of data modeling in TypeScript"
-description: "A deep dive into TypeScript to demonstrate the importance of data modeling"
+description: "Take a deep dive into TypeScript to explore the importance of data modeling"
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/the-importance-of-data-modeling-in-typescript.png
   alt: "The importance of data modeling in TypeScript"

datetime-picker.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Building a datetime picker for a database"
-description: "How we built a next-gen datetime picker for a next-gen database."
+description: "Learn how we built a next-generation datetime picker for a next-generation database."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/date-time-picker-for-databases.png
   alt: Xata
@@ -34,13 +34,16 @@ All of Xata’s datetimes are saved and returned with the UTC timezone.
 
 Xata has two main personas:
 
+* Developers 
+* Low-code users
+
 ##### Developers
 
 At it’s core, Xata is a database aimed at developers.
 
 Developers are power users: They’re comfortable with not leaving their keyboard, they understand datetime strings, and, most of all, they love and respect the UTC timezone.
 
-##### Low code users
+##### Low-code users
 
 Entrepreneurs, hackers, customer success, you name it.
 

hackmamba.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Hackmamba jamstack content hackathon 2.0"
-description: "Learning, writing, and networking during two full weeks! This last Hackmamba Jamstack Content Hackathon 2.0. was quite a journey!"
+title: "Hackmamba Jamstack Content Hackathon 2.0"
+description: "Learning, writing, and networking for two full weeks"
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/hackmamba.png
   alt: Winnders
@@ -30,4 +30,4 @@ You can find all published posts https://dev.to/hackmamba
 
 These articles are great if you're looking for some good examples to get started with Xata. If you're looking to try Xata out as the year winds down, be sure to enter your app in the [Xata Challenge](https://xata.io/challenge)!
 
-Come chat with us on [discord](https://xata.io/discord) if you have any questions or simply want to talk data.
+Chat with us on [Discord](https://xata.io/discord) if you have any questions or simply want to talk data.

hello-world.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Hello, world! Xata raises $5M for a new type of serverless database"
-description: "If you haven't heard of us before, it's because we haven't launched yet. We're busy building the product, but we don't believe in stealth mode, so we'd rather talk to you about what we're building and why."
+description: "Learn what Xata is and how it can revolutionize your development experience."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/hello-world.png
   alt: Xata

how-to-fuzzy-search-with-xata.mdx

@@ -1,6 +1,6 @@
 ---
 title: "How to fuzzy search with Xata"
-description: "Xata is a serverless database built on PostgreSQL with data automatically replicated to Elasticsearch. This opens a whole new world of possibilities when it comes to free text search. Deep dive into Queen Raae's favorite Xata feature, fuzzy search."
+description: "Explore the world of free text search possibilities with Xata and take a deep dive into fuzzy search."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/how-to-fuzzy-search-with-xata.png
   alt: How to Fuzzy Search with Xata
@@ -28,7 +28,7 @@ Fuzzy search to the rescue! 💪
 
 > **FYI:** The example code uses a Xata Worker using the Xata SDK + a React component using ReactQuery. However, you may use any type of server-side + client-side setup you are comfortable with.
 
-## Fuzzy Search Is Enabled by Default
+## Fuzzy search is enabled by default
 
 Xata search functionality comes with the `fuzziness` param set to `1` by
 default, letting the user make one typo, such as one wrong character
@@ -126,7 +126,7 @@ export default function App() {
 Other possible levels of `fuzziness` are `0`, to disable it altogether, and `2`
 to extend the allowed typo tolerance. Higher than `2` is not supported.
 
-## Highlight the Relevant Text
+## Highlight the relevant text
 
 In addition to expecting a more forgiving search, users expect to know precisely
 _why_ a result matches their search term. With a fuzzy search, that is even more
@@ -238,7 +238,7 @@ export default function App() {
 }
 ```
 
-## Search Playground
+## Search playground
 
 Xata even allows you to play around with search—no code needed—using the Search
 Engine Playground.
@@ -255,7 +255,7 @@ coding.
   position="center"
 />
 
-## Where To Go From Here?
+## Where to go from here?
 
 I hope you are excited to dig into fuzzy search with Xata:
 

how-xata-powers-search-for-rankone.mdx

@@ -1,6 +1,6 @@
 ---
-title: "How Xata powers search for RankOne’s social platform"
-description: "How RankOne is using Xata to bring streamers closer to their audience."
+title: "Xata powers search for RankOne’s social platform"
+description: "RankOne is using Xata to bring streamers closer to their audience."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/community-spotlight-rankone.png
   alt: Rankone

jamstack-a-deep-dive.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Jamstack: a deep dive"
-description: "This post is an in-depth look at the Jamstack, how it compares to other alternatives, and how Xata aims to complete it by providing a serverless database."
+description: "Explore Jamstack, its alternatives, and how Xata complements it with a serverless database."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/jamstack-mern-lamp-stack-comparison.png
   alt: Xata

new-starters.mdx

@@ -1,6 +1,6 @@
 ---
-title: "New starter templates for Xata"
-description: "To help in your journey with Xata, we are providing more and more starters! Today will be about SolidStart, Astro, and SvelteKit. Have fun!"
+title: "Take a closer look at Xata's latest starter templates"
+description: "Begin your Xata journey with our new starters - SolidStart, Astro, and SvelteKit."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/new-starters-solidstart-sveltekit-astro.png
   alt: Winnders

offsite-for-a-fully-remote-team.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Offsite for our fully remote team"
-description: "Last week we did our first Xata off-site, in Marbella, Spain. This is a photo-blog post about how it went and what we've learned from it. Warning: this post might make you hungry."
+title: "Coming together to build Xata"
+description: "Take a look at our photo-blog post about Xata's first off-site, featuring insights on our learnings."
 image:
   src: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/offsite-for-a-fully-remote-team.png
   alt: Xata
@@ -10,11 +10,11 @@ published: true
 slug: offsite-for-a-fully-remote-team
 ---
 
-Xata is a fully remote team with employees in Spain, Germany, Andorra, Belgium, and the US, with plans to add more countries soon. To compensate for our mostly Zoom-based work lives, we’re meeting in person a few times per year for an offsite in a nice location.
+Xata is a fully remote team with employees located in Spain, Germany, Andorra, Belgium, and the US, and we have plans to expand to more countries soon. To make up for our primarily Zoom-based work culture, we arrange to meet in person several times per year at an offsite location.
 
-Last week, we had our first such offsite in Marbella, Spain, and here is how we did it and what we have learned from it.
+Last week, we had our first such offsite in Marbella, Spain, and here is how we did it and what we learned from it.
 
-Fair warning: the photos in this post might make you hungry.
+Warning: the photos in this post might make you hungry.
 
 ## Preparation
 
@@ -47,7 +47,8 @@ The game plan was:
 
 Like in a conference where the most valuable track is the “hallway track”, more important than the agenda was what we discussed during breaks, during dinners, or simply on the bus. So we made sure the schedule had plenty of breathing air for us to know each other.
 
-## Monday: arrivals
+## Monday
+### Arrivals
 
 For many of us, this was the day that we met in person for the first time, despite working together for several months already. This made everyone very excited to meet each other. When we reached the hotel, the Xatafly — which is how we nicknamed our logo — was there to welcome us.
 
@@ -63,7 +64,8 @@ In the evening we had our first dinner with the whole team, and we learned quick
 />
 ![Dinner on the first evening](/images/blog/marbella/IMG_6425.jpg)
 
-## Tuesday: Team, strategy, and messaging
+## Tuesday
+### Team, strategy, and messaging
 
 We started by discussing our [Series A](https://xata.io/blog/xata-series-a-announcement) announcement and what it means for our overall strategy. We then did a team retrospective which was a very open discussion and gave us a lot of food for thought. Speaking of food, the frequent “coffee breaks” included a lot more than coffee, more like a full buffet. It’s ok, we can diet the week after.
 
@@ -89,7 +91,8 @@ Dinner was again fabulous.
   position="center"
 />
 
-## Wednesday: Planning and roadmap
+## Wednesday 
+### Planning and roadmap
 
 A few brave people started the day early with a workout at the hotel gym. The rest of us found reasonable excuses to not do that.
 
@@ -117,7 +120,8 @@ In the evening, for a change, we cooked our own food! Our amazing teacher Jose s
   position="center"
 />
 
-## Thursday: Fun day
+## Thursday
+### Fun day
 
 We started the day by walking down to the port of Marbella for a Catamaran trip. The water was choppy which means that we didn’t see dolphins as we were hoping but the waves kept us entertained.
 
@@ -132,7 +136,8 @@ After another delicious lunch, we visited Cueva del Tesoro and the beautiful cit
   position="center"
 />
 
-## Friday: travel back home
+## Friday
+### Travel back home
 
 After dinner on Thursday evening, we hugged and said goodbye, because many of us had flights or trains early in the morning on Friday. Others could stay a bit more and enjoy the beautiful weather.
 
@@ -145,7 +150,7 @@ After dinner on Thursday evening, we hugged and said goodbye, because many of us
   position="center"
 />
 
-## Learnings and conclusions
+## Takeaways and conclusions
 
 - There was a lot of laughter during the off-site. Coming after the long pandemic and the associated social distancing, it reminded us just how important laughing together is.
 - As a remote-first company, we do a lot of work async and in writing. Meeting each other for a few days did wonders in associating a friendly voice and tone with future written comments.