diff --git a/README.md b/README.md
index 042e4f2d..2e17069f 100644
--- a/README.md
+++ b/README.md
@@ -9,31 +9,31 @@ from the _*.proto_ files in this repository:
 
 There are five primary service families, which inter-operate on entities 
 controlled by one (or more) Ed25519 keypairs:
-1. The [cryptocurrency service](services/CryptoService.proto),
+1. The [cryptocurrency service](services/crypto_service.proto),
 for cryptocurrency accounts with transfers denominated 
 in [hBar (ℏ)](https://help.hedera.com/hc/en-us/articles/360000674317-What-are-the-official-HBAR-cryptocurrency-denominations-).
-2. The [consensus service](services/ConsensusService.proto), for
+2. The [consensus service](services/consensus_service.proto), for
 fast and unbiased ordering of opaque binary messages exchanged on 
 arbitrary topics.
-3. The [smart contract service](services/SmartContractService.proto), for
+3. The [smart contract service](services/smart_contract_service.proto), for
 execution of Solidity contract creations and calls; contract may both possess
 ℏ themselves and exchange it with non-contract accounts.
-4. The [file service](services/FileService.proto), for storage and 
+4. The [file service](services/file_service.proto), for storage and 
 retrieval of opaque binary data.
-5. The [token service](services/TokenService.proto), for token related operations such as create, update, mint, burn, transfer etc.
+5. The [token service](services/token_service.proto), for token related operations such as create, update, mint, burn, transfer etc.
 
 There are also three secondary service families:
-1. The [network service](hedera/NetworkService.proto), for operations scoped
+1. The [network service](services/network_service.proto), for operations scoped
 to the network or its constituent nodes rather user-controlled entities as above.
-2. The [scheduling service](services/ScheduleService.proto), for scheduling a transaction to 
+2. The [scheduling service](services/schedule_service.proto), for scheduling a transaction to 
 be executed when the ledger has received enough prequisite signatures. 
-3. The [freeze service](hedera/FreezeService.proto), for use by 
+3. The [freeze service](services/freeze_service.proto), for use by 
 privileged accounts to suspend network operations during a maintenance window.
 
 It is important to note that most network services are gated by fees which 
 must be paid in ℏ from a cryptocurrency account. The payer authorizes a
 fee by signing an appropriate transaction with a sufficient subset of the 
-Ed25519 key(s) associated to their account.
+Ed25519/ECDSA(secp256k1) key(s) associated to their account.
 
 # Branching
 This repository uses a simple branching model with only two distinguished branches: