Rename GDS doc file

nasa · Nov 21, 2024 · cf03e60 · cf03e60
1 parent 323e650
commit cf03e60
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...cumentation/user-manual/gds/user_guide.md → ...ion/user-manual/gds/gds-test-api-guide.md b/...cumentation/user-manual/gds/user_guide.md → ...ion/user-manual/gds/gds-test-api-guide.md
@@ -24,7 +24,7 @@ def test_send_command(fprime_test_api):
 To run this test, ensure the GDS is running (by invoking `fprime-gds`) and then run `pytest test/int/test_my_deployment.py`.
 
 > [!NOTE]
-> TODO: rename this file. You must ensure that your deployment has been built as this is required by `fprime-gds` and the integration test API.
+> You must ensure that your deployment has been built as this is required by `fprime-gds` and the integration test API.
 
 
 ## Usage Patterns

diff --git a/docs/documentation/user-manual/overview/development-practice.md b/docs/documentation/user-manual/overview/development-practice.md
@@ -207,7 +207,7 @@ To add a component to the topology:
 As the topology comes together, it is helpful to write system-level tests for subsystems of the
 overall deployment. This makes sure that as a system, top-level requirements are met.
 
-The fprime-gds has a python API that can be used to write integration test cases that support sending commands, checking for events, and getting telemetry channel readings. To get started with writing integration tests, check out the [GDS integration test guide](../gds/user_guide.md).
+The fprime-gds has a python API that can be used to write integration test cases that support sending commands, checking for events, and getting telemetry channel readings. To get started with writing integration tests, check out the [GDS integration test guide](../gds/gds-test-api-guide.md).
 
 ## Conclusion