fix GFM links
This commit is contained in:
@@ -40,7 +40,7 @@ Jump to: [General](#general_terms) |
|
||||
|
||||
|
||||
### General Terms
|
||||
|
||||
|
||||
##### Chipping away
|
||||
The process of removing sample text from templates when that text
|
||||
does not apply to the current project. Often some of the sample text
|
||||
@@ -97,7 +97,7 @@ After you have done what the sticky note says, you can delete the
|
||||
sticky note.
|
||||
|
||||
### Computer Science and Technology Terms
|
||||
|
||||
|
||||
|
||||
##### ::API (Application Programming Interface)
|
||||
An API is a set of functions that one software component makes
|
||||
@@ -112,7 +112,7 @@ server in order to invoke an operation on the server-side.
|
||||
[More information on SOAP](http://directory.google.com/Top/Computers/Programming/Internet/Web_Services/SOAP/?tc=1).
|
||||
|
||||
### Process Terms
|
||||
|
||||
|
||||
|
||||
##### Change Control Board (CCB)
|
||||
A group of people who review proposed changes to the project
|
||||
@@ -162,7 +162,7 @@ The term "release number" by itself refers to an
|
||||
of the existence of any internal release numbers.
|
||||
|
||||
### Development Tool Terms
|
||||
|
||||
|
||||
#### Version Control System
|
||||
::DEFINITION1
|
||||
|
||||
@@ -191,7 +191,7 @@ of the existence of any internal release numbers.
|
||||
::DEFINITION1
|
||||
|
||||
### Requirements Terms
|
||||
|
||||
|
||||
#### Feature specification
|
||||
A feature specification focuses on one feature of a software product
|
||||
and completely describes how that feature can be used. It includes a
|
||||
@@ -211,12 +211,12 @@ show how the actor uses several features to accomplish a goal.
|
||||
A user or an external system that uses the system being built.
|
||||
|
||||
### Design Terms
|
||||
|
||||
|
||||
#### ::TERM2
|
||||
::DEFINITION2
|
||||
|
||||
### Design Goals Terms
|
||||
|
||||
|
||||
#### Correctness
|
||||
This design correctly matches the given requirements.
|
||||
|
||||
@@ -306,7 +306,7 @@ Users can apply their knowledge of similar UIs or UI standards to
|
||||
this system.
|
||||
|
||||
### QA Terms
|
||||
|
||||
|
||||
#### Bug
|
||||
*n.* **Deprecated** since 1991. See [defect](#defect).
|
||||
|
||||
@@ -337,7 +337,7 @@ reported in a defect report. Developers use failure evidence during
|
||||
debugging to eventually find and remove [defects](#defect).
|
||||
|
||||
### QA Goals Terms
|
||||
|
||||
|
||||
#### 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
|
||||
|
Reference in New Issue
Block a user