3) If a generic title is present, prefer these canonical titles:

- `/// note | 注意`

Notes:

- `details` blocks exist; keep `/// details` as-is and translate only the title after `|`.
- Example canonical titles used in existing docs:

```
/// details | 上述指令的含義
```

```
/// details | 關於 `requirements.txt`

		return slices.Contains(buckets, bucket)
	}
}

// Details for the measured bandwidth
type Details struct {
	LimitInBytesPerSecond            int64   `json:"limitInBits"`
	CurrentBandwidthInBytesPerSecond float64 `json:"currentBandwidth"`
}

// BucketBandwidthReport captures the details for all buckets.
type BucketBandwidthReport struct {
	BucketStats map[BucketOptions]Details `json:"bucketStats,omitempty"`
}

                    See <a href="https://bt-internal-docs.grdev.net/gbt/how-to/release/release-troubleshooting/#binary-compatibility-check-failed-">the documentation</a> for more details.
                  </div>
                </details>
                <details>
                  <summary>
                    If change was made on the `release` branch but hasn't yet been merged to `master`, merge `release` to `master`:

     *
     * @param crudMode the CRUD mode
     * @param id the duplicate host ID
     * @return HTML response for the duplicate host details page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse details(final int crudMode, final String id) {
        verifyCrudMode(crudMode, CrudMode.DETAILS, this::asListHtml);
        saveToken();

body:
  - type: markdown
    attributes:
      value: "Our proposal process is documented here: https://go.dev/s/proposal-process"
  - type: textarea
    id: proposal-details
    attributes:
      label: "Proposal Details"
      description: "Please provide the details of your proposal here."
    validations:

    //                                               Details
    //                                               -------
    /**
     * Displays the job log details page.
     *
     * @param crudMode the CRUD mode
     * @param id the job log ID
     * @return HTML response for the details page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse details(final int crudMode, final String id) {

// GNU Affero General Public License for more details.
//
// You should have received a copy of the GNU Affero General Public License
// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package cmd

// Format related consts
const (
	// Format config file carries backend format specific details.
	formatConfigFile = "format.json"
)

const (

Avec `openapi_examples` ajouté à `Body()`, le `/docs` ressemblerait à :

<img src="/img/tutorial/body-fields/image02.png">

## Détails techniques { #technical-details }

/// tip | Astuce

Si vous utilisez déjà **FastAPI** en version **0.99.0 ou supérieure**, vous pouvez probablement **passer** ces détails.

Ils sont plus pertinents pour les versions plus anciennes, avant que OpenAPI 3.1.0 ne soit disponible.

- `/// note | 참고`
- `/// tip | 팁`
- `/// warning | 경고`
- `/// info | 정보`
- `/// danger | 위험`
- `/// note Technical Details | 기술 세부사항`
- `/// check | 확인`
Notes:

- `details` blocks exist in Korean docs; keep `/// details` as-is and translate only the title after `|`.

Alle diese Parameter können anders als „`static`“ lauten, passen Sie sie an die Bedürfnisse und spezifischen Details Ihrer eigenen Anwendung an.

## Weitere Informationen { #more-info }