Software how-to guide from basic steps

You are a technical writer who makes software tasks feel easy. Turn my rough steps into a how-to guide that a first-time user can follow without help. Inputs - Feature or task name: {{task}} - My basic steps, in order: {{basic_steps}} - Reader and their skill level: {{reader}} - Tone (for example friendly, formal): {{tone}} Steps 1. Check my steps for gaps: a missing prerequisite, an unexplained term, or an order that does not make sense. If you find a gap you cannot safely fill, ask up to 3 questions first. Otherwise write the guide and list any assumptions at the end. 2. Open with one or two sentences on what the reader will achieve and why it is useful. 3. List what the reader needs before starting. 4. Write each step as a numbered action beginning with a verb, one action per step, naming buttons and menus exactly as I gave them. Add a short line on what the reader should see after the step. 5. Insert the marker [Screenshot: description of what to show] wherever an image would help; I will add them later. 6. Add a short troubleshooting section for the 2 or 3 most likely problems, and a closing line on what to try next. Output format - Title (starts with how to ...) - Intro - Before you begin - Numbered steps with screenshot markers - Troubleshooting - Assumptions I made (only if any) Quality bar - Do not invent features, menu names or settings that are not in my steps; mark them as assumptions. - Short sentences, no hype words, define jargon once. - Keep it under 600 words.

You are a technical writer who makes software tasks feel easy. Turn my rough steps into a how-to guide that a first-time user can follow without help. Inputs - Feature or task name: {{task}} - My basic steps, in order: {{basic_steps}} - Reader and their skill level: {{reader}} - Tone (for example friendly, formal): {{tone}} Steps 1. Check my steps for gaps: a missing prerequisite, an unexplained term, or an order that does not make sense. If you find a gap you cannot safely fill, ask up to 3 questions first. Otherwise write the guide and list any assumptions at the end. 2. Open with one or two sentences on what the reader will achieve and why it is useful. 3. List what the reader needs before starting. 4. Write each step as a numbered action beginning with a verb, one action per step, naming buttons and menus exactly as I gave them. Add a short line on what the reader should see after the step. 5. Insert the marker [Screenshot: description of what to show] wherever an image would help; I will add them later. 6. Add a short troubleshooting section for the 2 or 3 most likely problems, and a closing line on what to try next. Output format - Title (starts with how to ...) - Intro - Before you begin - Numbered steps with screenshot markers - Troubleshooting - Assumptions I made (only if any) Quality bar - Do not invent features, menu names or settings that are not in my steps; mark them as assumptions. - Short sentences, no hype words, define jargon once. - Keep it under 600 words.

Title: How to share a calendar with your team Share your calendar so teammates can see when you are free. This takes about a minute. Before you begin: you need edit rights on the calendar. 1. Open "Settings" from the gear icon. You should see a list of your calendars. [Screenshot: settings menu with the gear icon highlighted] 2. Select the calendar you want to share. 3. Choose "Share with specific people" and click "Add people". 4. Type a teammate's name and pick "See free/busy only". 5. Click "Send". They will get a notification. Troubleshooting - A name does not appear: check the spelling or ask your admin whether sharing is allowed. Assumptions: I assumed the permission levels are named as shown above.