FLUT-958979 - [Feature] Cleared grammatical issues for date range picker and calendar

[ManiKesavaraj]

Feature description

• Task Link - [FLUT-958981]
• Need to clear grammatical issues, paraphrasing for both date range picker and calendar widget.
• Need to correct the grammatical mistakes for above mentioned linear and radial gauges Section in the Flutter User Guide documentation widget by using the Syncfusion Continue AI.

Analysis and design

Copy the UG content with code snippet and modify it in Continue AI based on the shared prompt. Modify the shared prompt based on your needs if needed.

Replace the hyperlink given by the AI with the original hyperlink.
Ensure naming casing of the widget.
Replace the existing code snippet alignment with AI code snippet in proper alignment.

Prompt:
Use the prompt below for UG review in AI-Continue.
Review the following User Guide(UG) document based on the criteria below. After reviewing, rewrite and share the updated content. If any modifications are made during the review, clearly indicate what was changed and why.
Review Criteria:

• Spelling: Identify and correct any spelling errors.
• Grammar: Fix grammatical mistakes and awkward phrasing to improve readability.
• Technical Accuracy: Ensure the correct usage of technical terms, product names, and APIs (e.g., Syncfusion, Flutter).
• Formatting: Verify proper formatting for code blocks, markdown syntax, and hyperlinks.
• Consistency: Maintain consistent terminology, phrasing, and capitalization throughout the document.
• Clarity: Improve sentence structure and flow while preserving technical accuracy and intent.
• Tone: Maintain a professional, developer-friendly, and instructional tone appropriate for technical documentation.
• Links & References: Check that all links are functional and point to relevant, up-to-date resources.
• Tags: Suggest relevant tags or keywords based on the document’s content for categorization and searchability.

Solution description

Checked and cleared the grammatical issues, paraphrasing for all the date range picker and calendar widget UG documentation pages.

Output screenshots

Post the output screenshots if an UI is affected or added due to this feature.

Areas affected and ensured

No, areas affected.

API Changes

List all API changes here (or just put None), example:

Added:

• string ListView.GroupName { get; set; } //Bindable Property
• int ListView.GroupId { get; set; } // Bindable Property
• void ListView.Clear ();

Changed:

• object ListView.SelectedItem => Cell ListView.SelectedItem

Behavioral Changes

No behavioral changes.

Test cases

Provide the unit testing written file details to understand the use cases considered in this implementation.
If there is no TDD (if it’s not possible to follow), provide the UI automation script location and the Excel file that contains the use cases considered in this implementation.
Provide the test cases Excel file alone if the feature cannot be automated in any case.

List out all the scenarios you have tested after include these changes. You can refer the predefined scenarios from below link.

https://syncfusion.atlassian.net/wiki/display/CHARTXAMARIN/Chart+Test+Plan

Testbed sample location

Provide the test bed sample location where code reviewers can review the new feature’s behaviors. This depends on the CI process that your team follows. It can be from NPMCI, HockeyApp, staging site, local server, etc.

Does it have any known issues?

No.

Does it have memory leak?

Not applicable.

MR CheckList

• Does it follow the design guidelines? It is mandatory that, we should not move the changes without reading this.
• Did UI automation passed without errors? If it is customer issue, make sure it is included in the IR automation.
• Properly working in Xamarin.Forms previewer.
• Ensured in iOS, Android, UWP and macOS (if supported).
• Have you added API comments if it is new API?
• Does it need localization? If so, update resx file in GitHub.
• Whether we have added new APIs? If so, whether it is as per the guidelines?
• If changes are made in the Xamarin.Forms sample browser project file, whether it is included in the props file too? If not, your sample level changes will not reflect in the application published in the hockey app.
• Have you ensured the changes in Android API 19 and iOS 9?

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: FLUT-958979-Correct-grammatical-errors-in-the-UG-for-the-Date-Range-Picker

[SyncfusionBuild]

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: FLUT-958979-Correct-grammatical-errors-in-the-UG-for-the-Date-Range-Picker
Image Alt Text Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
Image Size Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
Image Name Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
FT Layout Syntax Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
Front matter Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
File Path Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)
MD Tag Validation Error(s): 0 (Critical: 0, High: 0, Medium: 0, Low: 0, Info: 0)