docs(navigation-drawer): remove nav tag since it is added from the component itself

[desig9stein]

Related to IgniteUI/igniteui-angular#14847

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in topic content has a valuable update, it's new or considered as preview\ beta
• link to other topics using ../relative/path.md
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check broken links (use browser add-on)
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)
• add pending-localization label when the review of the PR is done
• add a member from the localization team to translate it

[Copilot]

Pull request overview

Updates the Navigation Drawer documentation examples to avoid wrapping drawer content in an extra <nav> element when the component already provides the appropriate semantic container.

Changes:

• Removes <nav> wrappers from several igxDrawer template examples in KR/EN/JP docs.
• Updates KR router examples formatting to remove the <nav> wrapper around repeated drawer items.
• Fixes JP reference list formatting at the end of the topic.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
kr/components/navdrawer.md	Removes <nav> wrappers from drawer templates, including router examples.
jp/components/navdrawer.md	Removes <nav> wrappers from examples and normalizes the final reference list formatting.
en/components/navdrawer.md	Removes <nav> wrappers from the introductory examples (but one <nav> remains later in the Router section).

Comments suppressed due to low confidence (1)

jp/components/navdrawer.md:354

• Prefer property binding for routerLink here as well (e.g., [routerLink]="item.link") instead of routerLink="{{item.link}}". This avoids interpolation in an attribute value and keeps the RouterLink directive input typed consistently.

    <span
      *ngFor="let item of componentLinks"
      routerLink="{{item.link}}"
      routerLinkActive
      #rla="routerLinkActive"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This doc removes the extra <nav> wrapper in the early examples, but there is still a <nav> wrapper later in the same file in the "Using Angular Router" example (around line 347). That leaves the topic inconsistent with the stated goal (and can reintroduce nested <nav> landmarks if the component already renders one). Please remove that remaining <nav> wrapper or clarify why it is required specifically in that section.

[Copilot]

In Angular templates, prefer property binding for routerLink instead of string interpolation in an attribute. Using [routerLink]="item.link" (or an array form) avoids unnecessary string interpolation and keeps the directive input typed as intended.

[Copilot]

Same as above: use property binding for routerLink (e.g., [routerLink]="item.link") rather than routerLink="{{item.link}}" to keep the RouterLink input typed and avoid interpolation in attribute values.