diff options
| author | sin | 2015-03-06 16:53:48 +0000 |
|---|---|---|
| committer | sin | 2015-03-06 16:53:48 +0000 |
| commit | e060d02f72c2a2e9f1252d60705424336b74af46 (patch) | |
| tree | c1c0061cdda23714e53e2a1ab539cb39a794f8eb | |
| parent | df61e9484fcbeca7d573d194f4b1433a9b517ba4 (diff) | |
Update section names in README
| -rw-r--r-- | README | 8 |
1 files changed, 4 insertions, 4 deletions
| @@ -7,8 +7,8 @@ in GCC and clang. It was initially designed to be used on musl[1] based Linux | |||
| 7 | distributions. | 7 | distributions. |
| 8 | 8 | ||
| 9 | 9 | ||
| 10 | Why? | 10 | Features |
| 11 | ==== | 11 | ======== |
| 12 | 12 | ||
| 13 | - It is portable, works on *BSD and Linux systems. | 13 | - It is portable, works on *BSD and Linux systems. |
| 14 | - It will only trap non-conformant programs. This means that fortify | 14 | - It will only trap non-conformant programs. This means that fortify |
| @@ -21,8 +21,8 @@ Why? | |||
| 21 | resulting binary. | 21 | resulting binary. |
| 22 | 22 | ||
| 23 | 23 | ||
| 24 | How to use? | 24 | Sample usage |
| 25 | =========== | 25 | ============ |
| 26 | 26 | ||
| 27 | A plan for integrating fortify into a system is still in planning stages. | 27 | A plan for integrating fortify into a system is still in planning stages. |
| 28 | If you want to quickly test it, you can try something like the following: | 28 | If you want to quickly test it, you can try something like the following: |