changelog build over christmas (#14227)

* just to get a changleog build over christmas

* happy holidays

Author: edwinyjlim

contents/handbook/content/docs.mdx

@@ -16,9 +16,9 @@ At PostHog, we want our docs to win over developers and to give us a competitive
 
 ### 1. Treat docs like a product
 
-We treat our docs like a product, because they are. They have users (readers), use cases (implementation, product education, troubleshooting, etc.), and success metrics (more on this later). PostHog's goal is to help customers build successful products, and docs play a huge part in that.
+We treat our docs like a product, because they are. They have users (readers), use cases (implementation, product education, troubleshooting, etc.), and success metrics (more on this later). PostHog's goal is to help customers build successful products and docs play a huge part in that.
 
-The blend of roles docs have presents unique challenges and opportunities. But ultimately, great docs can drive product activation by providing the *right* information, in the *right* way, at the *right* stage in a [developer's journey](https://res.cloudinary.com/dmukukwp6/image/upload/dev_journey_9ed427d2c5.webp). 
+Developer docs present unique challenges and opportunities. But ultimately, great docs can drive product activation by providing the *right* information, in the *right* way, at the *right* stage in a [developer's journey](https://res.cloudinary.com/dmukukwp6/image/upload/dev_journey_9ed427d2c5.webp). 
 
 This could mean helping developers set up their very first PostHog event in a new framework. This could also mean helping existing customers with complex configurations and custom properties smoothly integrate their third or fourth PostHog product. It's a wide spectrum, but the goal is the same: to help developers self-serve and succeed with PostHog.