{"action":"closed","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/6045","repository_url":"https://api.github.com/repos/eslint/eslint","labels_url":"https://api.github.com/repos/eslint/eslint/issues/6045/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/6045/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/6045/events","html_url":"https://github.com/eslint/eslint/issues/6045","id":152668072,"number":6045,"title":"Inconsistent typography and terminology in `indent` documentation","user":{"login":"Trott","id":718899,"avatar_url":"https://avatars.githubusercontent.com/u/718899?v=3","gravatar_id":"","url":"https://api.github.com/users/Trott","html_url":"https://github.com/Trott","followers_url":"https://api.github.com/users/Trott/followers","following_url":"https://api.github.com/users/Trott/following{/other_user}","gists_url":"https://api.github.com/users/Trott/gists{/gist_id}","starred_url":"https://api.github.com/users/Trott/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Trott/subscriptions","organizations_url":"https://api.github.com/users/Trott/orgs","repos_url":"https://api.github.com/users/Trott/repos","events_url":"https://api.github.com/users/Trott/events{/privacy}","received_events_url":"https://api.github.com/users/Trott/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint/labels/accepted","name":"accepted","color":"0052cc"},{"url":"https://api.github.com/repos/eslint/eslint/labels/documentation","name":"documentation","color":"5319e7"},{"url":"https://api.github.com/repos/eslint/eslint/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-02T23:24:13Z","updated_at":"2016-05-04T21:34:14Z","closed_at":"2016-05-04T21:34:14Z","body":"<!--\r\nThis template is for bug reports. If you are reporting a bug, please continue on. If you are here for another reason, please see below:\r\n\r\n1. To propose a new rule: http://eslint.org/docs/developer-guide/contributing/new-rules\r\n2. To request a change: http://eslint.org/docs/developer-guide/contributing/changes\r\n3. If you have any questions, please stop by our chatroom: https://gitter.im/eslint/eslint\r\n\r\nNote that leaving sections blank will make it difficult for us to troubleshoot and we may have to close the issue.\r\n-->\r\n\r\n**What version of ESLint are you using?**\r\n\r\nmaster branch\r\n\r\n**What parser (default, Babel-ESLint, etc.) are you using?**\r\n\r\nn/a\r\n\r\n**Please show your full configuration:**\r\n\r\nn/a\r\n\r\n**What did you do? Please include the actual source code causing the issue.**\r\n\r\nMarkdown documentation is not consistent about putting configuration options like `SwitchCase` in backticks. It is also a bit loose in that it uses that term to mean `case` clauses in `switch` statements. I'm not sure the typical user will understand that terminology use. (Perhaps it comes from the AST?)\r\n\r\n**What did you expect to happen?**\r\n\r\nI expected the markdown to be consistent in its usage of typography and precise in its usage of terminology. (Sorry if that sounds persnickity. Not meant that way. Just trying to not put `n/a` for everything.)\r\n\r\n**What actually happened? Please include the actual, raw output from ESLint.**\r\n\r\nThe terminology and typography is imprecise and/or inconsistent."}}