--- # This file is licensed under the MIT License (MIT) available on # http://opensource.org/licenses/MIT. layout: base lang: en breadcrumbs: - dev docs - glossary - GLOSSARY_ENTRY_TITLE end_of_page: | --- {% capture filename %}{{page.filename}}{% endcapture %} {% include helpers/subhead-links.md %}
{% capture markdown_content %} # {{page.required.title_max_40_characters_no_formatting}}
This definition comes from the [technical glossary](/en/developer-glossary).
## Definition {% autocrossref %} {{page.required.summary_max_255_characters_no_formatting}} {% endautocrossref %} ### Synonyms {% for synonym in page.required.synonyms_shown_in_glossary_capitalize_first_letter %} * {{synonym}} {% endfor %} {% if page.optional.not_to_be_confused_with_capitalize_first_letter %} ### Not To Be Confused With {% autocrossref %} {% for term in page.optional.not_to_be_confused_with_capitalize_first_letter %} * {{term}} {% endfor %} {% endautocrossref %} {% endif %} {% if page.optional.links_html_or_markdown_style_capitalize_first_letter %} ### Links {% for link in page.optional.links_html_or_markdown_style_capitalize_first_letter %} * {{link}} {% endfor %} {% endif %} {% include references.md %} {{site.glossary_links}} {% endcapture %} {{ markdown_content | markdownify }}{% comment %}Why is this hack necessary? I don't get why this template can't be natively rendered as markdown like the releases template.{% endcomment %}