docs(core): update Trezor Core references

diff --git a/common/defs/README.md b/common/defs/README.md
index 819c82d3..e52241fc 100644
--- a/common/defs/README.md
+++ b/common/defs/README.md
@@ -5,7 +5,7 @@ This directory hosts JSON definitions of recognized coins, tokens, and FIDO/U2F
 ## FIDO
 
 The [`fido/`](fido) subdirectory contains definitons of apps whose logos and
-names are shown on Trezor T screen for FIDO/U2F authentication.
+names are shown on Trezor Core screen for FIDO/U2F authentication.
 
 Each app must have a single JSON file in the `fido/` subdirectory. Every app must have
 its `label` set to the user-recognizable application name. The `u2f` field is a list of
@@ -27,7 +27,7 @@ based on Bitcoin code.
 
 Each Bitcoin-like coin must have a single JSON file in the `bitcoin/` subdirectory,
 and a corresponding PNG image with the same name. The PNG must be 96x96 pixels and
-the picture must be a circle suitable for displaying on Trezor T.
+the picture must be a circle suitable for displaying on Trezor Core.
 
 Testnet is considered a separate coin, so it must have its own JSON and icon.
 
@@ -83,7 +83,7 @@ added to the dataset.
 We keep track of support status of each built-in coin over our devices. That is `T1B1`
 for Trezor One, `T2T1` for Trezor T, `T2B1` and `T3B1` for Trezor Safe 3 (both models
 should have identical entries, except for minimum versions which are higher on `T3B1`),
-`T3T1` for Trezor Safe 5.
+`T3T1` for Trezor Safe 5, `T3W1` for Trezor Safe 7.
 
 This information is stored in [`support.json`](support.json).
 External contributors should not touch this file unless asked to.
diff --git a/docs/common/bitcoin-signing.md b/docs/common/bitcoin-signing.md
index cebbd45e..ad6285fd 100644
--- a/docs/common/bitcoin-signing.md
+++ b/docs/common/bitcoin-signing.md
@@ -65,7 +65,7 @@ If all internal inputs are taproot, then the verification of the previous transa
 is skipped. This is possible because if the host provides invalid information about the
 UTXOs being spent, then the resulting taproot signatures will also be invalid.
 
-Trezor T also supports pre-signed inputs for multi-party signing. If an input has script
+Trezor Core also supports pre-signed inputs for multi-party signing. If an input has script
 type `EXTERNAL` and provides a signature, Trezor will validate the signature against the
 previous transaction in this step.
 
@@ -159,7 +159,7 @@ supplied to the transaction by verified external inputs are subtracted from the
 transaction total that the user is asked to confirm, whereas unverified
 external inputs are not subtracted.
 
-Verified external inputs are only supported on the Trezor T. They must either
+Verified external inputs are only supported on the Trezor Core. They must either
 already have a valid signature or they must come with an ownership proof. If
 the input already has a valid signature, then the host provides the
 `script_sig` and/or `witness` fields. If the other signing party hasn't signed
@@ -356,7 +356,7 @@ So the replacement transaction is, for example, allowed to:
 
 ## Payment requests
 
-In Trezor T a set of transaction outputs can be accompanied by a payment request.
+In Trezor Core a set of transaction outputs can be accompanied by a payment request.
 Multiple payment requests per transaction are also possible. A payment request is a
 message signed by a trusted party requesting payment of certain amounts to a set of
 outputs as specified in [SLIP-24](https://github.com/satoshilabs/slips/blob/master/slip-0024.md).