From b50f0b98b613ee123ef11b56e2b3274236f93103 Mon Sep 17 00:00:00 2001
From: Bhakti <76544741+Bhakti087@users.noreply.github.com>
Date: Sat, 12 Nov 2022 01:43:09 +0530
Subject: [PATCH]  minor change

---
 jobs/interviews/technical-writer.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/jobs/interviews/technical-writer.md b/jobs/interviews/technical-writer.md
index 8209273..9498e14 100644
--- a/jobs/interviews/technical-writer.md
+++ b/jobs/interviews/technical-writer.md
@@ -8,8 +8,8 @@
     - Nothing is set in stone. No voice & tone document. No detailed process. We are a startup.
     - What I'm looking for is someone eager to learn, who have a high attention to details (links in your resume, some links or spaces/break lines missing in your articles...), and can be somewhat autonomous.
 - What is your process to write about a technology you don't know yet?
-- How do you come up with the topics yourwant to write about on your blog?
+- How do you come up with the topics you want to write about on your blog?
 - Did you read our documentation? What would you improve?
-- If there's a new feature coming out soon that you don't have time to finish documenting, is it better to publish no docs or partial docs? Why?
+- Is it better to publish no docs or partial docs if a new feature is coming out soon and you don't have time to finish documenting it? Why?
 - Imagine that, by some miracle, there's nothing in the queue. No releases, no projects. What do you do?
 - What do you imagine your ideal team being?