Apply suggestions from code review

Author: adityaoberai

src/routes/blog/post/everyone-can-do-devrel-but-should-they/+page.markdoc

@@ -9,14 +9,13 @@ author: aditya-oberai
 category: devrel
 ---
 
-One thing that I can say, having spent five years in communities and over two years as a Developer Advocate at Appwrite, is that Developer Relations (or DevRel) isn’t just a job but a philosophy. DevRel is something we can do by helping developers in our communities, sharing knowledge through our content, or writing code and building projects. That being said, should everyone be rushing towards a job in Developer Relations? Recently, I have observed a bubble developing around this space. I want to take this blog as an opportunity to share my opinion on whether everyone should chase DevRel as a career.
+One thing that I can say, having spent six years in communities and over three years as a Developer Advocate at Appwrite, is that Developer Relations (or DevRel) isn’t just a job but a philosophy. DevRel is something we can do by helping developers in our communities, sharing knowledge through our content, or writing code and building projects. That being said, should everyone be rushing towards a job in Developer Relations? Recently, I have observed a bubble developing around this space. I want to take this blog as an opportunity to share my opinion on whether everyone should chase DevRel as a career.
 
 Before deciding whether everyone should become a DevRel professional, let’s discuss what DevRel is.
 
 # Understanding DevRel
 
 > Developer Relations, or DevRel, is a domain that focuses on maintaining relationships with the folks building on an organization's technologies or products.
-> 
 
 Essentially DevRel acts as the **bridge between the code and the community**. DevRel folks are often responsible for maintaining communication between organizations and developers to ensure a better information flow and feedback loop. Thus, both entities have a better experience and growth path.