lint: e.g., → for example

docs/pages/careers/react-engineer-docs-infra.md

@@ -44,7 +44,7 @@ And just like the products themselves, the documentation should reflect our fund
 
 Our internal docs-infra team currently shares responsibility for this domain, and they've developed features such as autogenerated OG images, multi-tab component demos, speed performance improvements, and more.
 
-There are so many other features we'd like to implement, and projects we could draw inspiration from (e.g., [Nextra](https://nextra.site/))—but the existing team (each of whom spends most of their time on one of our product engineering teams) simply doesn't have the bandwidth to take on bigger and more ambitious projects.
+There are so many other features we'd like to implement, and projects we could draw inspiration from (for example, [Nextra](https://nextra.site/))—but the existing team (each of whom spends most of their time on one of our product engineering teams) simply doesn't have the bandwidth to take on bigger and more ambitious projects.
 For example, we could offer visitors the ability to toggle the design language they want to view the docs in; add offline support; use AI to provide component demo customization; and so much more.
 
 That's why we're looking for a skilled full-stack developer to own the docs infrastructure as their full-time responsibility.