When declaring directives, the standalone flag is set to true by default in current Angular versions.

The docs for the directive decorator should correctly explain the default behavior, while still mentioning when to set it to false.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.dev application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

The current docs describe how to set the standalone flag of a directive to true to make the directive available to other components. The wording implies that it needs to be set explicitly, even though it is the default behavior in current versions of Angular.

What is the new behavior?

The documentation reflects the current behavior of the standalone flag and explains what needs to be done to declare a directive in a module instead.

Does this PR introduce a breaking change?

• Yes
• No

Other information