diff options
| author | Darren Bane <darren.bane@gmail.com> | 2020-07-31 00:16:21 +0100 |
|---|---|---|
| committer | Darren Bane <darren.bane@gmail.com> | 2020-07-31 00:16:21 +0100 |
| commit | 546c54613a397996e3faa04173bfa73a08a6ee47 (patch) | |
| tree | c74770668a3d896dbf7e48a0dff7a05a9bf5f8e4 /doc | |
| parent | 3a45de8cca52e72cc00b25b4eafaafb5a93f6b03 (diff) | |
| download | lsp-546c54613a397996e3faa04173bfa73a08a6ee47.tar.gz | |
Minor fixups
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/breaking_rules.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/breaking_rules.md b/doc/breaking_rules.md index c0f3272..0a88e01 100644 --- a/doc/breaking_rules.md +++ b/doc/breaking_rules.md @@ -90,6 +90,9 @@ The following technology is recommended: * The SBCL compiler. * ltk for the view layer. +For simple multi-user, +use the IRCv3 bots (nickserv, chanserv) and IRCCloud or similar. + The following is probably the most work that makes sense without earning money. @@ -124,9 +127,6 @@ I don't want to maintain my own. DbC would be another nice-to-have, but I settle for `(declare`. -Could do simple multi-user, -using the IRCv3 bots (nickserv, chanserv) and IRCCloud or similar - # Refinement to Production-Quality First, software at the level of the previous section is quite usable. @@ -172,7 +172,7 @@ bane 2008 However, some of this documentation is better in the source code: * The summary of functions should be taken care of by having the public functions and classes commented. -* The formal requirement for function behaviour can be donw with +* The formal requirement for function behaviour can be done with tables with Basic English \.[ basic english |