Skip to content

Commit 8449bc7

Browse files
Merge pull request #81 from input-output-hk/fraser-iohk/documentation-cleanup
wip: minor documentation cleanup
2 parents 2c225b8 + 73311e0 commit 8449bc7

2 files changed

Lines changed: 7 additions & 19 deletions

File tree

CONTRIBUTING.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ cabal build all
4747
Specific executables can be executed through cabal:
4848

4949
``` sh
50-
cabal run db-analyser
50+
cabal run kes-agent-control
5151
```
5252

5353
# Testing
@@ -83,26 +83,12 @@ This section contain guidelines on what to check when making a pull request.
8383
- When bumping version bounds on the dependencies *it is not necessary* to
8484
increase the package version number. See [this
8585
section](#updating-the-dependencies-bounds).
86-
- When you want to create a changelog entry, follow [this and the following
87-
section](docs/website/contents/for-developers/ReleaseProcess.md#installing-scriv).
88-
89-
## Following our git process
90-
91-
Our [git process](docs/website/contents/for-developers/GitProcess.md) describes
92-
the `git` practices we encourage when working with the code in this repository.
9386

9487
## Updating the documentation
9588

9689
When submitting a pull request, please look update the relevant parts of the
9790
documentation (see [this section](#documentation)).
9891

99-
## Following the style guide
100-
101-
We have a [Haskell style
102-
guide](docs/website/contents/for-developers/StyleGuide.md) that should be
103-
followed when writing code in Consensus. Our style guide is not set in stone,
104-
and improvements are always welcome.
105-
10692
## Formatting the code
10793

10894
We use `fourmolu` for ensuring a consistent formatting style.

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,12 @@ designed for forward security. In Cardano, we use this to sign blocks,
88

99
This forward security however requires that after a key has been evolved, all
1010
copies of the old key must be securely erased. This implies that KES keys must
11-
never be stored on disk. The KES Agent, then, exists so that keys aren't lost
12-
in the event of a restart.
11+
never be stored on disk. The KES Agent exists so that KES keys can be securely
12+
stored in memory, rather than on disk, and will manage the evolution of KES keys
13+
in place of the node, allowing for the keys to persist (in ephemeral storage)
14+
even over a restart of the node itself.
1315

14-
For further information, see [the Guide](docs/guide.markdown).
16+
For further information, see [the Guide](doc/guide.markdown).
1517

1618
## OS Compatibility
1719

@@ -58,7 +60,7 @@ Querying the KES agent to verify that it works:
5860
KES_AGENT_CONTROL_PATH=/path/to/control.socket kes-agent-control info
5961
```
6062

61-
For further information, see [the Guide](docs/guide.markdown).
63+
For further information, see [the Guide](doc/guide.markdown).
6264

6365
## License & Copyright
6466

0 commit comments

Comments
 (0)