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

Author: adityaoberai

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

@@ -32,7 +32,7 @@ Considering that DevRel can be viewed as an amalgam of **code**, **content**,
 
 My experience has taught me that, while there is always space to learn, as a DevRel practitioner (for example, Developer Advocate), you should gain experience on all three fronts (whether through dedicated jobs or by alternate means) before rushing into this career, and here is why:
 
-### Writing code 
+## Writing code 
 
 The time I spent learning how to build projects and working on real-world solutions (through self-defined problems or my internship) has substantially helped me in my DevRel journey. Understanding the pros and cons of the product I advocate for from a technical standpoint allows me to build a better sense of developer empathy for our community members. If I couldn’t build with our product, it would be impossible for me to relate to their problems and help solve them. Moreover, being able to code allows me to experience the Developer Experience of our product and offer feedback to our engineers, which enables better product development.