Skip to content

Commit 4f473cf

Browse files
authored
Merge pull request #3534 from edstenson/review_assertion_checking
Updated language use in cbmc-assertions.md
2 parents ca81c25 + d700224 commit 4f473cf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/cprover-manual/cbmc-assertions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,16 @@
44

55
[Assertions](http://en.wikipedia.org/wiki/Assertion_%28computing%29) are
66
statements within the program that attempt to capture the programmer's
7-
intent. The ANSI-C standard defines a header file
7+
intent. The ANSI C standard defines a header file
88
[assert.h](http://en.wikipedia.org/wiki/Assert.h), which offers a macro
9-
`assert(cond)`. When executing a statement such as
9+
`assert(cond)`. When executing a statement such as:
1010

1111
```C
1212
assert(p!=NULL);
1313
```
1414
1515
the execution is aborted with an error message if the condition
16-
evaluates to *false*, i.e., if `p` is NULL in the example above. The
16+
evaluates to *false*, that is, if `p` is NULL in the example above. The
1717
CPROVER tools can check the validity of the programmer-annotated
1818
assertions statically. Specifically, the CPROVER tools will check that
1919
the assertions hold for *any* nondeterministic choice that the program
@@ -49,7 +49,7 @@ if(i>=0 && i<100)
4949
```
5050
5151
The nondeterministic choice will guess the element of the array that is
52-
nonzero. The code fragment above is therefore equivalent to
52+
nonzero. The code fragment above is therefore equivalent to:
5353
5454
```C
5555
int a[100], i;

0 commit comments

Comments
 (0)