Correct docs in import with Diff

[iwahbe]

The behavior of import changed with pulumi/pulumi#19339, and our docs should reflect the current behavior.

Proposed changes

Unreleased product version (optional)

Related issues (optional)

[claude]

Documentation Review

I've reviewed the changes to the import documentation. Overall, this PR accurately reflects the behavior change from pulumi/pulumi#19339. Here are my findings:

✅ Positive Changes

1. Improved note formatting (lines 46-48): Moving the Python import underscore note from a code comment to a proper notes shortcode improves visibility and follows documentation conventions.

2. Accurate behavior update (lines 199-217): The new text correctly describes that imports now succeed and update resources to match program inputs, rather than failing on mismatch. The example console output is helpful and realistic.

📝 Issues Found

1. Grammar issue (line 199)

File: content/docs/iac/concepts/resources/options/import.md:199

The phrase "the import will succeed and then the resource will be modified" could be clearer. Consider:

If the resource's arguments differ from the imported state, the import will succeed, and the resource will then be modified to reflect the inputs in your Pulumi program.

Rationale: Adding a comma after "succeed" improves readability in this compound sentence.

2. Terminology consistency (line 220)

File: content/docs/iac/concepts/resources/options/import.md:220

The term "import-update" is introduced without prior explanation and may be confusing. Consider:

Because of auto-naming, it is common to see this update during import when you import a resource's name property.

Rationale: "import-update" is not a standard Pulumi term and may confuse readers. The revised text is clearer and more natural.

3. Code block language tag (line 201)

File: content/docs/iac/concepts/resources/options/import.md:201

The code fence uses console but according to STYLE-GUIDE.md, console output should use output or bash for commands. Since this shows command + output, consider splitting or using bash:

Replace the console code fence with bash for consistency with the style guide.

Rationale: Consistency with style guide for code block language tags.

Summary

The PR successfully updates the documentation to reflect the new import behavior. The three issues above are minor style and clarity improvements. The content is technically accurate and the example is helpful.

---

Need additional reviews or want me to help fix these issues? Mention @claude in a comment.

[iwahbe]

@claude Please implement your suggestions. For (3), let's use bash.

[claude]

Claude finished @iwahbe's task —— View job

---

Implementing Review Suggestions

Tasks

• Read current file state
• Apply grammar fix (line 199)
• Apply terminology consistency fix (line 220)
• Change code block language tag from console to bash (line 201)
• Commit and push changes

Summary

I've successfully implemented all three review suggestions:

1. Grammar fix (line 199): Added a comma after "succeed" to improve readability: "the import will succeed, and the resource will then be modified..."

2. Terminology consistency (line 220): Replaced the unclear "import-update" term with clearer phrasing: "it is common to see this update during import when you import..."

3. Code block language tag (line 201): Changed the code fence from console to bash for consistency with the style guide.

All changes have been committed and pushed to the PR branch.

--- |

[pulumi-bot]

Your site preview for commit c56e459 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16580-c56e459e.s3-website.us-west-2.amazonaws.com.