diff --git a/docs/changelog.md b/docs/changelog.md
index ff0cf3f26943..e2d27eee521b 100644
--- a/docs/changelog.md
+++ b/docs/changelog.md
@@ -16,7 +16,7 @@ description: >-
 **Testnet:** June 17, 2021
 {% endhint %}
 
-A new account balance file format was introduced in the Hedera Services v0.12.0 release. An [AccountBalanceFile.proto](https://github.com/hashgraph/hedera-protobufs/blob/main/streams/AccountBalanceFile.proto) has been added to the hedera-protobufs repository. The new file along with its signature file is compressed using gzip compression. Both the CSV file format and proto file format will exist in the same path and with the same name apart from the file extension being pb.gz and pb\_sig.gz. 
+A new account balance file format was introduced in the Hedera Services v0.12.0 release. An [AccountBalanceFile.proto](https://github.com/hashgraph/hedera-protobufs/blob/main/streams/account_balance_file.proto) has been added to the hedera-protobufs repository. The new file along with its signature file is compressed using gzip compression. Both the CSV file format and proto file format will exist in the same path and with the same name apart from the file extension being pb.gz and pb\_sig.gz. 
 
 Account Balance Proto File Name Example: 
 
diff --git a/docs/release-notes/mirror-node.md b/docs/release-notes/mirror-node.md
index 3fcbad8c89ad..5f6fa62a6320 100644
--- a/docs/release-notes/mirror-node.md
+++ b/docs/release-notes/mirror-node.md
@@ -274,7 +274,7 @@ We now expose the raw transaction bytes encoded in Base64 format in the REST API
 
 After scheduled transactions were made available in previewnet, we listened to user feedback and further iterated on the design to make it easier to use. This release adds support for this [revised scheduled transactions](https://github.com/hashgraph/hedera-services/blob/master/docs/scheduled-transactions/revised-spec.md) design planned to be released in HAPI v0.13. There was no impact to our REST API format, only the importer needed to be updated to parse and ingest the new proto format. Our monitor API and acceptance tests will be adjusted in the next release once the SDKs add support for the new design.
 
-This release also adds support for the newly announced account balance file format that was released in HAPI v0.12. The new [protobuf](https://github.com/hashgraph/hedera-protobufs/blob/main/streams/AccountBalanceFile.proto)based format will eventually replace the CSV format in July 2021. Until then, both formats will exist simultaneously in the bucket so users can transition at their leisure. Besides being more efficient to parse, the new files are also compressed using Gzip for reduced storage and download costs. We also took the time to improve the balance file parsing performance regardless of format. Average parse times should decrease by about 27%.
+This release also adds support for the newly announced account balance file format that was released in HAPI v0.12. The new [protobuf](https://github.com/hashgraph/hedera-protobufs/blob/main/streams/account_balance_file.proto)based format will eventually replace the CSV format in July 2021. Until then, both formats will exist simultaneously in the bucket so users can transition at their leisure. Besides being more efficient to parse, the new files are also compressed using Gzip for reduced storage and download costs. We also took the time to improve the balance file parsing performance regardless of format. Average parse times should decrease by about 27%.
 
 For our REST API, we now expose an `entity_id` field on our transactions related APIs. This field represents the main entity associated with that transaction type. For example, if it was a HCS transaction it would be the topic ID created, updated, or deleted.
 
diff --git a/docs/sdks/schedule-transaction/schedule-faq.md b/docs/sdks/schedule-transaction/schedule-faq.md
index dfc24212a352..62529d8609a9 100644
--- a/docs/sdks/schedule-transaction/schedule-faq.md
+++ b/docs/sdks/schedule-transaction/schedule-faq.md
@@ -12,7 +12,7 @@ Yes, the entity ID is referred to as the schedule ID which is returned in the re
 
 ## 3. What transactions can be scheduled?
 
-In its early iteration, users can schedule CryptoTransfer and ConsensusSubmitMessage transactions. All other transactions types will be available to schedule in future releases. The complete list of transactions that users can schedule in the future can be found [here](https://github.com/hashgraph/hedera-protobufs/blob/develop/services/SchedulableTransactionBody.proto#L76).
+In its early iteration, users can schedule CryptoTransfer and ConsensusSubmitMessage transactions. All other transactions types will be available to schedule in future releases. The complete list of transactions that users can schedule in the future can be found [here](https://github.com/hashgraph/hedera-protobufs/blob/develop/services/schedulable_transaction_body.proto#L76).
 
 ## 4. How can I find a schedule transaction that requires my signature?