chore: fix broken training documentation links (hiero-ledger#1737)

Signed-off-by: ParasSalonia <parassalonia22@gmail.com>
Signed-off-by: Paras Salonia <parassalonia22@gmail.com>

Author: ParasSalonia

CHANGELOG.md

@@ -251,12 +251,12 @@ This changelog is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.
 - Update changelog workflow to trigger automatically on pull requests instead of manual dispatch (#1567)
 - Formatted key-related unit test files (`key_utils_test.py`, `test_key_format.py`, `test_key_list.py`) using the black formatter
 - Add return type hint to `ContractId.__str__`. (#1654)
-
 - chore: update maintainer guidelines link in MAINTAINERS.md (#1605)
 - chore: update merge conflict bot message with web editor tips (#1592)
 - chore: update MAINTAINERS.md to include new maintainer Manish Dait and sort maintainers by GitHub ID. (#1691)
 
 ### Fixed
+- Corrected broken documentation links in SDK developer training files.(#1707)
 - Fixed assignment limit check to only count issues (not PRs) towards the maximum 2 concurrent assignments, allowing users to be assigned to PRs without affecting their issue assignment capacity. (#1717)
 - Updated Good First Issue recommendations to supported Hiero repositories. (#1689)
 - Fix the next-issue recommendation bot to post the correct issue recommendation comment. (#1593)

docs/sdk_developers/training/query.md

@@ -410,13 +410,13 @@ balance = query.execute(client)
 
 The SDK includes several production-ready query implementations that demonstrate best practices for extending `Query`. Contributors are encouraged to review these examples when implementing new queries:
 
-- [`account_balance_query.py`](../../examples/query/account_balance_query.py) — Simple query with minimal configuration
-- [`account_info_query.py`](../../examples/query/account_info_query.py) — Paid query with structured response
-- [`token_info_query.py`](../../examples/query/token_info_query_fungible.py) — Fungible token metadata
-- [`token_nft_info_query.py`](../../examples/query/token_nft_info_query.py) — NFT token metadata
-- [`topic_info_query.py`](../../examples/query/topic_info_query.py) — Streaming-style topic message retrieval
-- [`transaction_get_receipt_query.py`](../../examples/query/transaction_get_receipt_query.py) — Transaction receipt lookup
-- [`transaction_record_query.py`](../../examples/query/transaction_record_query.py) — Transaction record retrieval
+- [`account_balance_query.py`](../../../examples/query/account_balance_query.py) — Simple query with minimal configuration
+- [`account_info_query.py`](../../../examples/query/account_info_query.py) — Paid query with structured response
+- [`token_info_query.py`](../../../examples/query/token_info_query_fungible.py) — Fungible token metadata
+- [`token_nft_info_query.py`](../../../examples/query/token_nft_info_query.py) — NFT token metadata
+- [`topic_info_query.py`](../../../examples/query/topic_info_query.py) — Streaming-style topic message retrieval
+- [`transaction_get_receipt_query.py`](../../../examples/query/transaction_get_receipt_query.py) — Transaction receipt lookup
+- [`transaction_record_query.py`](../../../examples/query/transaction_record_query.py) — Transaction record retrieval
 
 These examples illustrate consistent usage of `_make_request()`, `_get_query_response()`, and `_get_method()` without duplicating execution or payment logic.
 

docs/sdk_developers/training/setup/05_network_client_setup.md

@@ -52,4 +52,4 @@ print(f"🎉 Created new token on the Hedera network with ID: {token_id}")
 ```
 
 ### Extra Support
-Read about Network and Client in more detail [here](docs/sdk_developers/training/network_and_client.md)
+Read about Network and Client in more detail [here](../network_and_client.md)

docs/sdk_developers/training/setup/06_importing_hiero_files.md

@@ -71,6 +71,6 @@ print(f"🎉 Created new token on the Hedera network with ID: {token_id}")
 ## Extra Support
 It takes time to be familiar with where everything is located to import correctly. 
 
-- For reference, look at the [examples](examples/) 
-- For an explanation of the project structure read [project_structure.md](docs/sdk_developers/training/setup/project_structure.md).
-- Set up [Pylance](docs/sdk_developers/pylance.md) to help you spot errors in your import locations
+- For reference, look at the [examples](../../../../examples)
+- For an explanation of the project structure read [project_structure.md](project_structure.md)
+- Set up [Pylance](https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance) to help you spot errors in your import locations