Skip to content

Commit 017434c

Browse files
committed
Correct spelling of GPG
1 parent 23370cb commit 017434c

File tree

5 files changed

+5
-5
lines changed

5 files changed

+5
-5
lines changed

docs/admin/authentication/account-recovery.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ size={{ width: '450px', height: 'auto' }}
7878

7979
In order to be accepted, the organisation key should meet these requirements:
8080

81-
- The key should be public gpg key
81+
- The key should be public GPG key
8282
- The key should use the algorithm RSA
8383
- The key should have a length of 4096 bits
8484
- The key should have a passphrase

docs/hosting/_includes/fromSource/_installation-steps.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ $ gpg --armor --export-secret-keys email@domain.tld > /var/www/passbolt/config/g
8282
$ gpg --armor --export email@domain.tld > /var/www/passbolt/config/gpg/serverkey.asc
8383
```
8484

85-
### 5. Initialize the gpg keyring
85+
### 5. Initialize the GPG keyring
8686

8787
You no longer need to be connected as www-data from now. In order for passbolt authentication to work your server key needs to be in the keyring used by the web server.
8888

docs/hosting/_includes/helm/_helm-install-usage.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Update this variable with the server name you plan to use. You will find at the
3636
<>{props.productName === 'PRO' && <ValuesProYaml />}</>
3737
</div>
3838

39-
If you are creating your own gpg keys the following commands can help convert them into a base64 encoded single line string which is what the values.yaml file expects.
39+
If you are creating your own GPG keys the following commands can help convert them into a base64 encoded single line string which is what the values.yaml file expects.
4040

4141
```bash
4242
gpg --armor --export-secret-keys <email you created keys with> | base64 -w 0

docs/hosting/faq/how-to-rotate-server-gpg-keys.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Ensure the fingerprint from private key is the same:
6565
sudo gpg --show-keys /etc/passbolt/gpg/serverkey_private.asc | grep -Ev "^(pub|sub|uid|$|sec|ssb)" | tr -d ' '
6666
```
6767

68-
CentOS 7 gpg command is quite old and has no `–show-keys` parameter. Use these commands instead:
68+
CentOS 7 `gpg` command is quite old and has no `–show-keys` parameter. Use these commands instead:
6969
```bash
7070
# public key fingerprint
7171
sudo cat /etc/passbolt/gpg/serverkey.asc | gpg --with-fingerprint - | grep -Ev "^(pub|sub|uid|$)" | tr -d ' ' | sed 's/Keyfingerprint=//'

docs/hosting/troubleshooting/logs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ The healthcheck is used to check whether the Passbolt system is running as expec
4848

4949
### Datacheck
5050

51-
The datacheck is a great tool as it aims to have a look at the data integrity for gpg keys, authentication tokens, groups, resources, etc.
51+
The datacheck is a great tool as it aims to have a look at the data integrity for GPG keys, authentication tokens, groups, resources, etc.
5252

5353
**Package Installation**
5454
```bash

0 commit comments

Comments
 (0)