GFM changes

Glossary-Std.md

@@ -338,50 +338,50 @@ debugging to eventually find and remove [defects](#defect).
 
 ### QA Goals Terms
 
-#### Functionality > Correctness
+#### Functionality > Correctness
 Correctness is the most basic quality goal. It means that, when
 valid inputs are given and the system is in a valid state and under
 reasonable load, the system's behavior and results will be correct.
 
-#### Functionality > Robustness
+#### Functionality > Robustness
 Robustness is the system's ability to gracefully handle
 invalid inputs. It should never be possible for any user input to
 crash the system or corrupt data, even if that user input is
 abnormal, unexpected, or malicious.
 
-#### Functionality > Accuracy
+#### Functionality > Accuracy
 Accuracy refers to the mathematical precision of calculations done
 by the system. Any system that does numeric calculations must
 consider accuracy, e.g., financial or scientific applications.
 
-#### Functionality > Compatibility
+#### Functionality > Compatibility
 Systems that claim to follow standards or claim compatibility with
 existing systems must adhere to the relevant file formats,
 protocols, and APIs. The relevant standards are linked at the top of
 this document.
 
-#### Functionality > Factual correctness
+#### Functionality > Factual correctness
 Is the data in the system a true representation of the real world?
 Any system that contains initial data or gathers data about the real
 world should be sure that the data is factually correct. E.g., a tax
 preparation program should embody correct and up-to-date facts about
 tax law.
 
-#### Usability > Understandability and Readability
+#### Usability > Understandability and Readability
 Users need to understand the system to use it. The basic metaphor
 should be understandable and appropriate to user tasks. Some defects
 in understandability include unclear metaphors, poor or hard-to-see
 labels, lack of feedback to confirm the effects of user actions, and
 missing or inadequate on-line help.
 
-#### Usability > Learnability and Memorability
+#### Usability > Learnability and Memorability
 Every user interface contains some details that users will need to
 learn and remember. E.g., Alt-F to open the "File" menu. UI cues and
 rules can make these details easier to learn and remember. E.g., the
 "F" is underlined and, as a rule, the first letter is usually the
 accelerator key.
 
-#### Usability > Task support
+#### Usability > Task support
 This is the quality of match between user tasks and the system's UI.
 Task support defects are cases where the system forces the user to
 take unnatural steps to accomplish a task or where the user is given
@@ -389,20 +389,20 @@ no support for a difficult step in a task. E.g., must the user
 invent an 8-character filename for their "Christmas card list"?
 E.g., must users total their own tax deductions?
 
-#### Usability > Efficiency
+#### Usability > Efficiency
 Users should be able to accomplish common tasks with
 reasonable effort. Common tasks should be possible with only one or
 two steps. The difficulty of each step should also be considered.
 E.g., does the user have to remember a long code number or click on
 a very small button?
 
-#### Usability > Safety
+#### Usability > Safety
 Humans are error-prone, but the negative effects of common errors
 should be limited. E.g., users should realize that a given command
 will delete data, and be asked to confirm their intent or have the
 option to undo.
 
-#### Usability > Consistency and Familiarity
+#### Usability > Consistency and Familiarity
 Users should be able to apply their past experience from other
 similar systems. This means that user interface standards should be
 followed, and common conventions should be used whenever possible.
@@ -413,7 +413,7 @@ that does demand it is a consistency defect, unless there is a real
 chance that the user is dealing with another currency on that step
 in his/her task.
 
-#### Usability > Subjective satisfaction
+#### Usability > Subjective satisfaction
 Users should feel generally satisfied with the UI. This is a
 subjective quality that sums up the other user interface qualities
 as well as aesthetics.
@@ -425,22 +425,22 @@ side-step security rule or exploit security holes. E.g., all user
 input should be validated and any malicious input should
 be rejected.
 
-#### Reliability > Consistency under load
+#### Reliability > Consistency under load
 Every system has some capacity limits. What happens when those
 limits are exceeded? The system should never lose or corrupt data.
 
-#### Reliability > Consistency under concurrency
+#### Reliability > Consistency under concurrency
 Systems that allow concurrent access by multiple users, or that use
 concurrency internally, should be free of race conditions
 and deadlock.
 
-#### Reliability > Availability under load
+#### Reliability > Availability under load
 Every system has some capacity limits. What happens when those
 limits are exceeded? The system should continue to service those
 requests that it is capable of handling. It should not crash or stop
 processing all requests.
 
-#### Reliability > Longevity
+#### Reliability > Longevity
 The system should continue to operate as long as it is needed. It
 should not gradually use up a limited resource. Example longevity
 defects include memory leaks or filling the disk with log files.
@@ -457,12 +457,12 @@ are increased. E.g., a file server might be scalable to a high
 number of users, or to very large files or very high capacity disks.
 Several specific scalability goals are listed below.
 
-#### Scalability > Performance under load
+#### Scalability > Performance under load
 This is a specific type of scalability goal dealing with the
 performance of the system at times when it is servicing many
 requests from many users.
 
-#### Scalability > Large data volume
+#### Scalability > Large data volume
 This is a specific type of scalability goal dealing with the ability
 for the system to handle large data sets. Operations should continue
 to be correct and efficient as data set size increases. Furthermore,
@@ -476,14 +476,14 @@ administrator recover from a crash? Is there sufficient log output
 to diagnose problems in the field? Can the system's data be backed
 up without downtime? Can the system be upgraded practically?
 
-#### Maintainability > Understandability
+#### Maintainability > Understandability
 Will it be easy for (future) developers to understand how the system
 works?
 
-#### Maintainability > Evolvability
+#### Maintainability > Evolvability
 Can the system easily be modified and extended over time?
 
-#### Maintainability > Testability
+#### Maintainability > Testability
 Can the system easily be tested? Do the requirements precisely
 specify possible inputs and the desired results? Can the system be
 tested in parts? When failures are observed, can they be traced back