terminal/doc/specs/spec-template.md

---
author: <first-name> <last-name> <github-id>/<email>
created on: <yyyy-mm-dd>
last updated: <yyyy-mm-dd>
issue id: <github issue id>
---

# Spec Title

## Abstract

[comment]: # Outline what this spec describes

## Inspiration

[comment]: # What were the drivers/inspiration behind the creation of this spec.

## Solution Design

[comment]: # Outline the design of the solution. Feel free to include ASCII-art diagrams, etc.

## UI/UX Design

[comment]: # What will this fix/feature look like? How will it affect the end user?

## Capabilities

[comment]: # Discuss how the proposed fixes/features impact the following key considerations:

### Accessibility

[comment]: # How will the proposed change impact accessibility for users of screen readers, assistive input devices, etc.

### Security

[comment]: # How will the proposed change impact security?

### Reliability

[comment]: # Will the proposed change improve reliability? If not, why make the change?

### Compatibility

[comment]: # Will the proposed change break existing code/behaviors? If so, how, and is the breaking change "worth it"?

### Performance, Power, and Efficiency

## Potential Issues

[comment]: # What are some of the things that might cause problems with the fixes/features proposed? Consider how the user might be negatively impacted.

## Future considerations

[comment]: # What are some of the things that the fixes/features might unlock in the future? Does the implementation of this spec enable scenarios?

## Resources

[comment]: # Be sure to add links to references, resources, footnotes, etc.
Docs: Contributor's guide and spec-template (#967) Submitting first draft of spec template, and `contributing.md` outlining our guidance on how to engage with us, file issues, suggest features, submit changes, etc. 2019-06-05 22:54:21 +02:00			`---`
			`author: <first-name> <last-name> <github-id>/<email>`
			`created on: <yyyy-mm-dd>`
			`last updated: <yyyy-mm-dd>`
			`issue id: <github issue id>`
			`---`

			`# Spec Title`

			`## Abstract`

			`[comment]: # Outline what this spec describes`

			`## Inspiration`

			`[comment]: # What were the drivers/inspiration behind the creation of this spec.`

			`## Solution Design`

			`[comment]: # Outline the design of the solution. Feel free to include ASCII-art diagrams, etc.`

			`## UI/UX Design`

			`[comment]: # What will this fix/feature look like? How will it affect the end user?`

			`## Capabilities`

			`[comment]: # Discuss how the proposed fixes/features impact the following key considerations:`

			`### Accessibility`

			`[comment]: # How will the proposed change impact accessibility for users of screen readers, assistive input devices, etc.`

			`### Security`

			`[comment]: # How will the proposed change impact security?`

			`### Reliability`

Fix a bunch of spelling errors across the project (#4295) Generated by https://github.com/jsoref/spelling `f`; to maintain your repo, please consider `fchurn` I generally try to ignore upstream bits. I've accidentally included some items from the `deps/` directory. I expect someone will give me a list of items to drop, I'm happy to drop whole files/directories, or to split the PR into multiple items (E.g. comments/locals/public). Closes #4294 2020-02-10 21:40:01 +01:00			`[comment]: # Will the proposed change improve reliability? If not, why make the change?`
Docs: Contributor's guide and spec-template (#967) Submitting first draft of spec template, and `contributing.md` outlining our guidance on how to engage with us, file issues, suggest features, submit changes, etc. 2019-06-05 22:54:21 +02:00
			`### Compatibility`

			`[comment]: # Will the proposed change break existing code/behaviors? If so, how, and is the breaking change "worth it"?`

			`### Performance, Power, and Efficiency`

			`## Potential Issues`

			`[comment]: # What are some of the things that might cause problems with the fixes/features proposed? Consider how the user might be negatively impacted.`

			`## Future considerations`

			`[comment]: # What are some of the things that the fixes/features might unlock in the future? Does the implementation of this spec enable scenarios?`

			`## Resources`

			`[comment]: # Be sure to add links to references, resources, footnotes, etc.`