The previous step has you cd out of your home directory, so adding ~/ to the source command makes it more likely to
Also, adds the `$` preface to the boost install steps, and updates the rippled version number for Boost compatibility info
- Delete folders for new pages that are handled by templates w/ no
markdown source
- Fully remove "Use Cases", leaving redirects for deleted pages.
- Move certain pages to new areas & remove Use Case markup
- Add "Contribute Code to the XRP Ledger" draft page
- Fix image paths in some Japanese-translated pages
- SVG diagrams can adapt to the visual theme of the site through CSS.
- Use the include_svg filter to include a diagram that adapts to the
theme.
- The styles/_diagrams.scss file controls the color mappings for
theme-aware digrams.
- Theme-aware diagrams are limited to specific colors and diagram
styles. Use UMLet or Google Draw and confirm that the diagram is still
legible when you build it.
- This commit updates existing diagrams in most places to be
theme-aware.
Docs indicate that validators should backup `validator-keys.json`, and not edit the backup. This causes problems when validator operators generate new validation tokens using backups of the `validator-keys.json` file. Specifically:
1. Validator operator copies backup of `validator-keys.json` to from backup location to validator
2. Operator generates a new token on validator
3. Operator deletes `validator-keys.json` from the validator
If the validator operator does not then increment the "token_sequence" in the backed up `validator-keys.json`, the next time the operator repeats the above three steps, their validations will be ignored by the network, as the resultant token will have a sequence number that is <= the last observed number.
