This week on Klariti we look at how to open older versions of MS Word .doc files in newer versions of Word. This can cause a lot of headaches especially if your legacy files you need to use and Word doesn’t appear to be able to open them.
What I’m going to show you is why this is happening, then walk through different methods to resolve it, and finally wrap up with some ‘best practices’ you can use for the next set of document conversions. We’ll also flag a few gotchas you need to watch out for.
Using ChatGPT as a technical writing assistant can significantly expedite the documentation process. However, as mentioned, it’s crucial to review and edit the generated content to ensure accuracy and clarity.
Let’s now look at how to write the actual prompt to summarize the text.
After you’ve uploaded the material to Chat-GPT/Claude/Poe, you must write a prompt (actually a series of prompts as can refine the summary results as you progress).
The simplest way to do this is to ask Chat-GPT how to create summaries, which is what I did.
A few months ago, I started experimenting with AI (Claude is my perference, fwiw) to see if it could help. My initial results were… ok but that’s all. It gave me generic, high-level ‘stuff’. But I didn’t give up. I realized the problem wasn’t the AI; it was my instructions. In AI speak, these are called ‘prompts’.
So, after a bit of trial and error, I learned to write more specific prompts. And the results really made a difference.
That’s part of the reason why I created the AI Prompt Toolkit for Business Continuity Planning. It’s the result of months of testing and refinement, so that you can craft better, more detailed, and truly personalized BCPs in less time.
Can CHAT-GPT write technical documentation? Like many tech writers, I’ve been looking at ways to use CHAT-GPT, Huggingface, and Google Bard to help with tech doc tasks.
In part 3 of this CHAT-GPT writing tutorial, we’re looking at how to use Chat-GPT to refine the first draft of your summary, especially those of a technical nature.