From aadf3f32419d0bb8d794ff34001f378550dc8b64 Mon Sep 17 00:00:00 2001
From: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Date: Mon, 12 Apr 2021 16:47:34 +0200
Subject: [PATCH 1/2] link pages to principles
---
guide/foundations/wallet-interoperability.md | 2 +-
guide/getting-started/open-design.md | 2 +-
guide/getting-started/personal-finance.md | 2 +-
guide/getting-started/user-research.md | 2 +-
guide/glossary.md | 2 +-
guide/onboarding/getting-to-know-your-users.md | 2 +-
guide/private-key-management/introduction.md | 2 +-
guide/private-key-management/multi-user-schemes.md | 2 +-
8 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/guide/foundations/wallet-interoperability.md b/guide/foundations/wallet-interoperability.md
index aa99e07ca..dbb196112 100644
--- a/guide/foundations/wallet-interoperability.md
+++ b/guide/foundations/wallet-interoperability.md
@@ -176,7 +176,7 @@ Per definition, multi signature wallets require interaction between all cosigner
layout = "float-right-desktop"
%}
-While it is extremely convenient when applications provide their own node connections, it is recommended to allow users to have a choice, and potentially even encourage them to set up their own node. This results in better decentralization, and also has privacy and security benefits.
+While it is extremely convenient when applications provide their own node connections, it is recommended to allow users to have a choice, and potentially even encourage them to set up their own node. This results in better [decentralization](/guide/foundations/principles/#decentralization), and also has privacy and [security](/guide/foundations/principles/#security) benefits.
diff --git a/guide/getting-started/open-design.md b/guide/getting-started/open-design.md
index 1d3d64b63..c1e8130aa 100644
--- a/guide/getting-started/open-design.md
+++ b/guide/getting-started/open-design.md
@@ -74,7 +74,7 @@ The best solutions typically come from a comprehensive understanding of the prob
Bitcoin has had the spirit of openness deeply embedded from its humble beginnings. The source code is public, participation in the network is public and unrestricted, and transferring value via the Bitcoin protocol is permissionless. Thousands of projects have copied ideas, techniques, and code from Bitcoin to experiment and explore different directions. So it provides a fantastic foundation for designers to also contribute in this open and participatory manner.
-One might argue that Bitcoin needs open design to stay true to its founding values. Most users don't interact directly with a technical protocol but with applications built on top of it. If those applications end up being controlled or manipulated, it will not matter if the protocol is open. So it is up to the people shaping the open-source application layer to help ensure that the future of Bitcoin remains decentralized and allows for permissionless participation.
+One might argue that Bitcoin needs open design to stay true to its founding values. Most users don't interact directly with a technical protocol but with applications built on top of it. If those applications end up being controlled or manipulated, it will not matter if the protocol is open. So it is up to the people shaping the open-source application layer to help ensure that the future of Bitcoin remains [decentralized](/guide/foundations/principles/#decentralization) and allows for permissionless participation.
## Values
diff --git a/guide/getting-started/personal-finance.md b/guide/getting-started/personal-finance.md
index 90ead14d6..26066039d 100644
--- a/guide/getting-started/personal-finance.md
+++ b/guide/getting-started/personal-finance.md
@@ -44,7 +44,7 @@ It still is possible to create simplified mental models that help us better unde
This section uses the traditional personal finance lens to think about what type of bitcoin products we may need. Because of bitcoin's unique properties, we cannot imitate conventional financial products and assume that the same solutions apply. And even if we could, this might be an excellent opportunity to take a fresh look and design new solutions for today's world. Bitcoin is also global by nature, so consider the unique circumstances of your users' lives.
-Let's take a look at six different categories of how somebody may want to organize their finances. Note that the following examples always assume that a user wants to keep as much self-custody as reasonable while balancing security and privacy.
+Let's take a look at six different categories of how somebody may want to organize their finances. Note that the following examples always assume that a user wants to keep as much [self-custody](/guide/foundations/principles/#self-custody) as reasonable while balancing [security](/guide/foundations/principles/#security) and [privacy](/guide/foundations/principles/#privacy).
1. Table of contents
{:toc}
diff --git a/guide/getting-started/user-research.md b/guide/getting-started/user-research.md
index 16a9c89e1..5d6911087 100644
--- a/guide/getting-started/user-research.md
+++ b/guide/getting-started/user-research.md
@@ -132,7 +132,7 @@ While we cannot know who is directly responsible for the activity, we can analyz
New technologies can take decades to reach adoption by mainstream audiences. Bitcoin is still early in the adoption curve, which affects research in multiple ways. Early adopters have different use cases and needs than users who will discover Bitcoin in the future. Products designed for today's user base may be inappropriate soon.
-Secondly, as the technology is maturing, its capabilities evolve as well. Scaling and performance improvements make complex transactions more affordable, better privacy, and security properties allow individuals to self-custody more comfortably and much more. There is an interplay between the size of the user base and the maturity of the technology.
+Secondly, as the technology is maturing, its capabilities evolve as well. Scaling and performance improvements make complex transactions more affordable, better privacy, and security properties allow individuals to [self-custody](/guide/foundations/principles/#self-custody) more comfortably and much more. There is an interplay between the size of the user base and the maturity of the technology.
For user research, this means that findings may become outdated quicker as they are closely linked to a specific point in time.
diff --git a/guide/glossary.md b/guide/glossary.md
index 96bbce971..d98c673dd 100644
--- a/guide/glossary.md
+++ b/guide/glossary.md
@@ -158,7 +158,7 @@ BIP44 instroduced the following structure, which BIP49 and BIP84 follow:
The path to the first address in a bitcoin-wallet using BIP84 will look like this:
`m/84h/0h/0h/0/0`
-For full interoperability a wallet should support all of these standards. More information can be found [here](https://learnmeabitcoin.com/technical/derivation-paths).
+For full [interoperability](/guide/foundations/principles/#interoperability) a wallet should support all of these standards. More information can be found [here](https://learnmeabitcoin.com/technical/derivation-paths).
## Extended private key (XPRIV)
diff --git a/guide/onboarding/getting-to-know-your-users.md b/guide/onboarding/getting-to-know-your-users.md
index 6c1a7d6cc..b86c3972c 100644
--- a/guide/onboarding/getting-to-know-your-users.md
+++ b/guide/onboarding/getting-to-know-your-users.md
@@ -36,7 +36,7 @@ This observation could take the form of [user research]({{ 'guide/getting-starte
* How did they hear about my application? Word of mouth? App store search?
* Do first-time users have specific needs or goals?
-Perhaps after research, you identify your users as "cypherpunks" with sound knowledge of Bitcoin, but they are new to your app. You might build an experience that preserves as much of their privacy as possible and is super customizable from the outset.
+Perhaps after research, you identify your users as "cypherpunks" with sound knowledge of Bitcoin, but they are new to your app. You might build an experience that preserves as much of their [privacy](/guide/foundations/principles/#privacy) as possible and is super customizable from the outset.
Aim to gather as much information and observations as possible in order to empathize with your users.
diff --git a/guide/private-key-management/introduction.md b/guide/private-key-management/introduction.md
index 27a5c86a1..faca002e1 100644
--- a/guide/private-key-management/introduction.md
+++ b/guide/private-key-management/introduction.md
@@ -31,7 +31,7 @@ scan this page to get an overview of the section and then decide which topics to
# Private key management
-When designing a bitcoin-application, the way you choose to manage the [private key]({{ '/guide/glossary/#private-key' | relative_url }}){:target="_blank"} often dictates the fundamental user experience for your users. Being in control of a private key means you have access to the funds it holds. Keeping that key safe is like being in charge of the security of your own bank. It comes with a lot of freedom, but also a big responsibility that many users are not used to.
+When designing a bitcoin-application, the way you choose to manage the [private key]({{ '/guide/glossary/#private-key' | relative_url }}){:target="_blank"} often dictates the fundamental user experience for your users. Being in control of a private key means you have access to the funds it holds. Keeping that key safe is like being in charge of the [security](/guide/foundations/principles/#security) of your own bank. It comes with a lot of freedom, but also a big responsibility that many users are not used to.
If it’s not secure enough, you risk loss of user's funds. But if it’s not convenient enough, you risk not getting or retaining many users in the first place.
diff --git a/guide/private-key-management/multi-user-schemes.md b/guide/private-key-management/multi-user-schemes.md
index f4dc4753d..2a23bc765 100644
--- a/guide/private-key-management/multi-user-schemes.md
+++ b/guide/private-key-management/multi-user-schemes.md
@@ -38,7 +38,7 @@ The use cases for shared schemes include spouses managing a joint account, group
As we saw with multi-key setups for personal use, a multi-key wallet has several controlling keypairs attached, or what is often called co-signers. The number of keys and required co-signers will depend on the use case. With spouses sharing a *joint account*, a simple 1-of-2 multi-key setup might suffice, meaning there are two keys but only one is required to sign for a transaction to be valid. At the other end of a spectrum a company might require a more complex 3-of-5 setup, requiring three of the five co-signers to approve any transaction.
-Just like with personal schemes, external signing devices can be used to hold one or several of the keys used for a shared multi-key setup. While this can increase security if managed correctly, the same caveat applies in terms of adding significant complexity.
+Just like with personal schemes, external signing devices can be used to hold one or several of the keys used for a shared multi-key setup. While this can increase [security](guide/foundations/principles/#security) if managed correctly, the same caveat applies in terms of adding significant complexity.
{% include image.html
image = "/assets/images/guide/private-key-management/schemes/shared-multi-key.jpg"
From 37e8608999f0071c232c47148847c5cf84aace80 Mon Sep 17 00:00:00 2001
From: Pavlenex <36959754+pavlenex@users.noreply.github.com>
Date: Tue, 13 Apr 2021 18:27:40 +0200
Subject: [PATCH 2/2] Update glossary.md
Co-Authored-By: Christoph Ono <695901+GBKS@users.noreply.github.com>
---
guide/glossary.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/guide/glossary.md b/guide/glossary.md
index d98c673dd..824a62c9c 100644
--- a/guide/glossary.md
+++ b/guide/glossary.md
@@ -152,13 +152,13 @@ There are several standards for how to notate the path to a key and correspondin
- [BIP49](https://github.com/bitcoin/bips/blob/master/bip-0049.mediawiki): multi-account, for script addresses with nested-SegWit
- [BIP84](https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki): multi-account, for SegWit addresses
-BIP44 instroduced the following structure, which BIP49 and BIP84 follow:
+BIP44 introduced the following structure, which BIP49 and BIP84 follow:
`m / purpose / coin_type / account / change / index`
The path to the first address in a bitcoin-wallet using BIP84 will look like this:
`m/84h/0h/0h/0/0`
-For full [interoperability](/guide/foundations/principles/#interoperability) a wallet should support all of these standards. More information can be found [here](https://learnmeabitcoin.com/technical/derivation-paths).
+For full [interoperability](/guide/foundations/principles/#interoperability) a wallet should support all of these standards. More information can be found [here](/guide/foundations/wallet-interoperability/#wallet-import-and-export) and [here](https://learnmeabitcoin.com/technical/derivation-paths).
## Extended private key (XPRIV)