update links to the blog posts that were moved

ivelum · Dec 30, 2024 · f9cb738 · f9cb738
1 parent 6463b76
commit f9cb738
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/content/how-we-work/how-1-full-stack.md b/content/how-we-work/how-1-full-stack.md
@@ -10,6 +10,6 @@ are skeptical about it being possible to find high-qualified full-stack
 developers. We know first-hand that it's hard but doable, and our team proves
 that it is possible. For most projects, it's a game changer.
 
-Read more in Teamplify blog:
-- [Why go full-stack in 2023?](https://teamplify.com/blog/why-go-full-stack/)
+Read more in our blog:
+- [Why go full-stack in 2023?](/blog/why-go-full-stack/)
 {.how-we-work--item-links}
diff --git a/content/how-we-work/how-3-efficient-communication.md b/content/how-we-work/how-3-efficient-communication.md
@@ -8,7 +8,7 @@ Productive communication and work transparency are crucial for project success.
 We prefer to have open team communication by default. It greatly helps us keep
 the team in sync and minimize distractions.
 
-Read more in Teamplify blog:
-- [Why work transparency matters?](https://teamplify.com/blog/why-work-transparency-matters/)
-- [Why public chats are better than direct messages](https://teamplify.com/blog/why-public-chats-are-better-than-direct-messages/)
+Read more in our blog:
+- [Why work transparency matters? (Teamplify)](https://teamplify.com/blog/why-work-transparency-matters/)
+- [Why public chats are better than direct messages](/blog/why-public-chats-are-better-than-direct-messages/)
 {.how-we-work--item-links}