{"action":"created","issue":{"url":"https://api.github.com/repos/GitbookIO/gitbook/issues/969","repository_url":"https://api.github.com/repos/GitbookIO/gitbook","labels_url":"https://api.github.com/repos/GitbookIO/gitbook/issues/969/labels{/name}","comments_url":"https://api.github.com/repos/GitbookIO/gitbook/issues/969/comments","events_url":"https://api.github.com/repos/GitbookIO/gitbook/issues/969/events","html_url":"https://github.com/GitbookIO/gitbook/issues/969","id":109987445,"number":969,"title":"Glossary should allow alternate terms","user":{"login":"mstade","id":605731,"avatar_url":"https://avatars.githubusercontent.com/u/605731?v=3","gravatar_id":"","url":"https://api.github.com/users/mstade","html_url":"https://github.com/mstade","followers_url":"https://api.github.com/users/mstade/followers","following_url":"https://api.github.com/users/mstade/following{/other_user}","gists_url":"https://api.github.com/users/mstade/gists{/gist_id}","starred_url":"https://api.github.com/users/mstade/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mstade/subscriptions","organizations_url":"https://api.github.com/users/mstade/orgs","repos_url":"https://api.github.com/users/mstade/repos","events_url":"https://api.github.com/users/mstade/events{/privacy}","received_events_url":"https://api.github.com/users/mstade/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/GitbookIO/gitbook/labels/feature","name":"feature","color":"fbca04"},{"url":"https://api.github.com/repos/GitbookIO/gitbook/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-06T11:23:10Z","updated_at":"2016-02-17T21:14:56Z","closed_at":null,"body":"Often times, variations of a word or phrase mean the same thing, and so should ideally be the same glossary entry. Here's an example, and proposed change to the glossary feature:\r\n\r\n```markdown\r\n# Function composition\r\n## Composable function\r\n\r\nFunction composition is ...\r\n```\r\n\r\nA regular markdown renderer would produce this, which I think is perfectly acceptable:\r\n\r\n# Function composition\r\n## Composable function\r\n\r\nFunction composition is ...\r\n\r\n---\r\n\r\nGitbook however, could be a bit smarter and recognize the (immediate) subheadings to produce something a bit nicer, perhaps something like the following:\r\n\r\n# Function composition\r\n*(Also: composable function)*\r\n\r\nFunction composition is ...\r\n\r\n---\r\n\r\nMost importantly, this would provide a way to refer different phrases to the same glossary entry."},"comment":{"url":"https://api.github.com/repos/GitbookIO/gitbook/issues/comments/185407313","html_url":"https://github.com/GitbookIO/gitbook/issues/969#issuecomment-185407313","issue_url":"https://api.github.com/repos/GitbookIO/gitbook/issues/969","id":185407313,"user":{"login":"torsday","id":281985,"avatar_url":"https://avatars.githubusercontent.com/u/281985?v=3","gravatar_id":"","url":"https://api.github.com/users/torsday","html_url":"https://github.com/torsday","followers_url":"https://api.github.com/users/torsday/followers","following_url":"https://api.github.com/users/torsday/following{/other_user}","gists_url":"https://api.github.com/users/torsday/gists{/gist_id}","starred_url":"https://api.github.com/users/torsday/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/torsday/subscriptions","organizations_url":"https://api.github.com/users/torsday/orgs","repos_url":"https://api.github.com/users/torsday/repos","events_url":"https://api.github.com/users/torsday/events{/privacy}","received_events_url":"https://api.github.com/users/torsday/received_events","type":"User","site_admin":false},"created_at":"2016-02-17T21:14:56Z","updated_at":"2016-02-17T21:14:56Z","body":"Man, this would be sweet"}}