You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Review the following developer documentation for quality and completeness.
Do not rewrite or elaborate — just identify and list issues that need correction,
organized by category:
MISSING STEPS
Any step a developer would need to complete the task that isn't documented
Implicit prerequisites (installs, config, permissions) not stated
Steps that assume prior knowledge without a link/reference
MISSING INFORMATION
Undocumented parameters, props, return values, or config options
Missing code examples where behavior is non-obvious
Missing version/compatibility notes (framework versions, package versions)
Missing error handling or troubleshooting guidance
Broken or missing links/references
TECHNICAL ACCURACY
Code samples that won't run as-is (syntax errors, outdated APIs, wrong imports)
Inconsistencies between text description and code sample
Outdated instructions (deprecated methods, old package names)
GRAMMATICAL / LANGUAGE ISSUES
Grammar, spelling, punctuation errors
Awkward phrasing or unclear sentences
Inconsistent terminology (e.g., same concept called two different names)
Inconsistent formatting (heading case, code block style, tone)
STRUCTURE / CLARITY
Logical ordering issues (step B before step A)
Redundant or duplicated content
Sections that don't match their heading
OUTPUT FORMAT:
For each issue found, list:
[Category] Location (section/heading/line) — Issue — Suggested fix (one line)
Keep the fix suggestions brief (one line each). Do not add general commentary,
praise, or lengthy explanations — just the issue list. If a category has no
issues, state "No issues found" under that heading.
Documentation to review:
[PASTE DOCUMENTATION HERE]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
1039164: Resolve Documentation Issues for Blazor PDF Viewer - Faq & Form
Examples PR: SyncfusionExamples/blazor-pdf-viewer-examples#138
Modified files:
Faq files:
Form files:
Prompt:
Review the following developer documentation for quality and completeness.
Do not rewrite or elaborate — just identify and list issues that need correction,
organized by category:
MISSING STEPS
Any step a developer would need to complete the task that isn't documented
Implicit prerequisites (installs, config, permissions) not stated
Steps that assume prior knowledge without a link/reference
MISSING INFORMATION
Undocumented parameters, props, return values, or config options
Missing code examples where behavior is non-obvious
Missing version/compatibility notes (framework versions, package versions)
Missing error handling or troubleshooting guidance
Broken or missing links/references
TECHNICAL ACCURACY
Code samples that won't run as-is (syntax errors, outdated APIs, wrong imports)
Inconsistencies between text description and code sample
Outdated instructions (deprecated methods, old package names)
GRAMMATICAL / LANGUAGE ISSUES
Grammar, spelling, punctuation errors
Awkward phrasing or unclear sentences
Inconsistent terminology (e.g., same concept called two different names)
Inconsistent formatting (heading case, code block style, tone)
STRUCTURE / CLARITY
Logical ordering issues (step B before step A)
Redundant or duplicated content
Sections that don't match their heading
OUTPUT FORMAT:
For each issue found, list:
[Category] Location (section/heading/line) — Issue — Suggested fix (one line)
Keep the fix suggestions brief (one line each). Do not add general commentary,
praise, or lengthy explanations — just the issue list. If a category has no
issues, state "No issues found" under that heading.
Documentation to review:
[PASTE DOCUMENTATION HERE]