Skip to content

Updated language use in Introduction #3529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 5, 2018
Merged

Updated language use in Introduction #3529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/cprover-manual/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@

Numerous tools to hunt down functional design flaws in silicon have been
available for many years, mainly due to the enormous cost of hardware
bugs. The use of such tools is wide-spread. In contrast, the market for
bugs. The use of such tools is widespread. In contrast, the market for
tools that address the need for quality software is still in its
infancy.

Research in software quality has an enormous breadth. We focus the
Research in software quality has enormous breadth. We focus the
presentation using two criteria:

1. We believe that any form of quality requires a specific *guarantee*,
Expand Down Expand Up @@ -40,4 +40,4 @@ formally verify such bounds by means of *unwinding assertions*. Once
this bound is established, CBMC is able to prove the absence of errors.

A more detailed description of how to apply CBMC to verify programs is
in the [CBMC Tutorial](../cbmc/tutorial/).
in our [CBMC Tutorial](../cbmc/tutorial/).