<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Writing Guides: Meeting Notes, Weekly Reports, PRDs and More</title>
<link>https://typdit.com/en/guides/</link>
<description>In-depth guides to the documents work runs on: meeting notes, weekly reports, PRDs, KPT retrospectives, blog drafts and reading notes. Every guide links to a ready-to-use template.</description>
<language>en</language>
<atom:link href="https://typdit.com/en/rss.xml" rel="self" type="application/rss+xml" />
<lastBuildDate>Sat, 10 Oct 2026 15:00:00 GMT</lastBuildDate>
<ttl>720</ttl>
<item>
<title>A Watermark in Your AI Draft Won't Show How Much You Rewrote</title>
<link>https://typdit.com/en/guides/how-to-keep-revision-history-for-ai-drafts/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-keep-revision-history-for-ai-drafts/</guid>
<pubDate>Sat, 10 Oct 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>There is a change worth knowing about if you take AI-generated drafts and turn them into reports or proposals. OpenAI and Anthropic have announced that they will add invisible watermarks to AI-generated text. But these marks tell you only that an AI system generated or processed part of the text. What you changed and what you verified still need to be documented separately in version histories and notes.</description>
</item>
<item>
<title>How to Decide Korean Spacing by Looking at the Word Before 만큼, 대로 and 지</title>
<link>https://typdit.com/en/guides/how-to-decide-korean-spacing/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-decide-korean-spacing/</guid>
<pubDate>Sat, 03 Oct 2026 15:00:00 GMT</pubDate>
<category>Writing</category>
<description>Confusion about spacing usually isn't a matter of not knowing the rules. A word with the same form can belong to a different part of speech depending on where it appears. '만큼' is joined to the preceding word in some sentences and separated by a space in others. Chapter 5 of the National Institute of Korean Language's Korean Orthography Rules (Hangeul Matchumbeop) sets out rules and explanations for these cases. All the examples below come from the original text of those rules.</description>
</item>
<item>
<title>If You Used AI in Your Manuscript, Here Is What to Tell Your Publisher</title>
<link>https://typdit.com/en/guides/how-to-disclose-ai-use-in-manuscript/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-disclose-ai-use-in-manuscript/</guid>
<pubDate>Sat, 03 Oct 2026 15:00:00 GMT</pubDate>
<category>Writing</category>
<description>If you used generative AI while writing a book, how much do you need to disclose? On September 29, 2026, 12 organizations, including the Korean Publishers Society, the Korea Publishing Research Institute, and the Writers' Association of Korea, released the first common standard addressing this question. Titled &quot;AI Use Principles for Publishers and Authors, for Readers&quot;, it consists of 5 chapters and 20 articles. These are voluntary principles with no legal force, but authors entering into agreements with publishers are likely to encounter them when drawing up a contract or submitting a manuscript.</description>
</item>
<item>
<title>What a Personal Essay Has to Settle Before the Sentences</title>
<link>https://typdit.com/en/guides/how-to-write-personal-essay/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-personal-essay/</guid>
<pubDate>Sat, 05 Sep 2026 15:00:00 GMT</pubDate>
<category>Writing</category>
<description>A draft that records what happened and stops at diary level is usually missing the thing you came to say. Five places, in order: separating situation from story, choosing material from what is still unsettled, putting the scene ahead of the reflection, deciding what to cut when other people appear, and stripping the moral out of the last paragraph.</description>
</item>
<item>
<title>Write the Introduction Last: How to Finish a Research Paper Draft</title>
<link>https://typdit.com/en/guides/how-to-write-research-paper/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-research-paper/</guid>
<pubDate>Wed, 02 Sep 2026 15:00:00 GMT</pubDate>
<category>Study</category>
<description>A paper is arranged in the order a reviewer reads it, not the order you discovered things. This guide covers the gap sentence, a reproducible methods section, keeping results apart from interpretation, and a drafting order that runs from methods to abstract.</description>
</item>
<item>
<title>What Gets a Book Manuscript Finished Is Not Inspiration but Page Count</title>
<link>https://typdit.com/en/guides/how-to-write-book-manuscript/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-book-manuscript/</guid>
<pubDate>Wed, 02 Sep 2026 15:00:00 GMT</pubDate>
<category>Writing</category>
<description>A long manuscript begins with inspiration and ends with page count. For anyone holding a first full-length draft: how to divide chapters and scenes, set a session quota and measure progress, build an outline and then shake it, separate rereading from rewriting, and judge a first draft differently from a revision.</description>
</item>
<item>
<title>Set the Introduction in Three Moves and the Report Follows</title>
<link>https://typdit.com/en/guides/how-to-write-assignment-report/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-assignment-report/</guid>
<pubDate>Sat, 22 Aug 2026 15:00:00 GMT</pubDate>
<category>Personal</category>
<description>When a report is told it drifted off topic, the cause sits in the introduction, not the body. Which conversation you are inside, what is still missing in it, what this piece will do about that. Once those three moves are in the introduction, every body heading becomes one share of that promise.</description>
</item>
<item>
<title>What Makes a Work Email Get a Fast Reply</title>
<link>https://typdit.com/en/guides/how-to-write-work-email/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-work-email/</guid>
<pubDate>Fri, 21 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>A reply is not late because the email is long. It is late because the reader has to search for what to do and by when. Here is the order that puts the ask up front, the habit of narrowing each email to one request, and real message mockups to compare.</description>
</item>
<item>
<title>What Actually Belongs in a Handover Document</title>
<link>https://typdit.com/en/guides/how-to-write-handover-doc/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-handover-doc/</guid>
<pubDate>Wed, 19 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>Handover documents get thick not because there is a lot to hand over, but because nobody knows what to hand over. Derive the outline backwards from where your successor actually gets stuck in week one, and the page gets shorter while it gets more useful.</description>
</item>
<item>
<title>Why the Cornell Method Still Beats Typing Faster</title>
<link>https://typdit.com/en/guides/how-to-take-lecture-notes/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-take-lecture-notes/</guid>
<pubDate>Wed, 19 Aug 2026 15:00:00 GMT</pubDate>
<category>Personal</category>
<description>Lecture notes are won in the minutes after class, not by hand speed. The longhand-beats-laptop consensus already wobbled under replication, and what separated the scores was transcription, not the tool.</description>
</item>
<item>
<title>How to Write a PRD Engineers Can Act On</title>
<link>https://typdit.com/en/guides/how-to-write-prd/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-prd/</guid>
<pubDate>Mon, 17 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>A good PRD opens with the problem, not a feature list. This guide walks through non-goals, verifiable requirement sentences and success metrics set before launch, with examples of each.</description>
</item>
<item>
<title>Running a KPT Retrospective That Actually Changes Things</title>
<link>https://typdit.com/en/guides/how-to-run-kpt-retrospective/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-run-kpt-retrospective/</guid>
<pubDate>Mon, 17 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>Teams whose retrospectives go nowhere confuse naming a problem with fixing it. This is the Keep-Problem-Try flow, a 60-minute time split, and how to carry experiments through to the next retro.</description>
</item>
<item>
<title>Why You Cannot Finish That Blog Post, and the Order That Fixes It</title>
<link>https://typdit.com/en/guides/how-to-finish-blog-draft/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-finish-blog-draft/</guid>
<pubDate>Mon, 17 Aug 2026 15:00:00 GMT</pubDate>
<category>Personal</category>
<description>A day of writing and deleting the same paragraph is not a talent problem, it is an order problem. This guide separates drafting from editing: push a terrible draft all the way to the end first, then bring it to life in revision.</description>
</item>
<item>
<title>A Reading Notes System for Books You Do Not Want to Forget</title>
<link>https://typdit.com/en/guides/how-to-keep-reading-notes/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-keep-reading-notes/</guid>
<pubDate>Mon, 17 Aug 2026 15:00:00 GMT</pubDate>
<category>Personal</category>
<description>When a finished book fades to a vague impression within a week, memory is not the culprit. This guide introduces a three-part note structure that goes past underlining, into your own words and application, backed by memory research.</description>
</item>
<item>
<title>How to Write Meeting Notes People Actually Reread</title>
<link>https://typdit.com/en/guides/how-to-write-meeting-notes/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-meeting-notes/</guid>
<pubDate>Sun, 16 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>Meeting notes are not a transcript, they are a record of decisions. Here is the structure and habit that make notes worth rereading, with bad and good examples side by side.</description>
</item>
<item>
<title>How to Write a Weekly Report in Five Minutes</title>
<link>https://typdit.com/en/guides/how-to-write-weekly-report/</link>
<guid isPermaLink="true">https://typdit.com/en/guides/how-to-write-weekly-report/</guid>
<pubDate>Sun, 16 Aug 2026 15:00:00 GMT</pubDate>
<category>Work</category>
<description>Weekly reports take long not because of writing skill, but because you are reconstructing a week from memory. Build the report from one line a day and a done-next-blocked structure, and Friday afternoon is yours again.</description>
</item>
</channel>
</rss>
