docs: Comment out TODOs (magma#12959)

Signed-off-by: Cameron Voisey <cameron.voisey@tngtech.com>
emakeev · Aug 5, 2022 · ac9cdd4 · ac9cdd4
1 parent 6fcf951
commit ac9cdd4
Show file tree

Hide file tree

Showing 11 changed files with 11 additions and 11 deletions.
diff --git a/docs/docusaurus/versioned_docs/version-1.1.X/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.1.X/lte/dev_notes.md
@@ -135,7 +135,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 If you need to debug MME with gdb, make sure all the services that it is

diff --git a/docs/docusaurus/versioned_docs/version-1.1.X/lte/s1ap_tests.md b/docs/docusaurus/versioned_docs/version-1.1.X/lte/s1ap_tests.md
@@ -8,7 +8,7 @@ original_id: s1ap_tests
 Current testing workflow for VM-only S1AP integration tests. We cover
 gateway-only tests and some general notes.
 
-TODO: Update this document once integration tests with cloud are also supported
+<!-- TODO: Update this document once integration tests with cloud are also supported -->
 
 Our VM-only tests use 3 Vagrant-managed VMs hosted on the local device (laptop):
 

diff --git a/docs/docusaurus/versioned_docs/version-1.2.X/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.2.X/lte/dev_notes.md
@@ -135,7 +135,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 If you need to debug MME with gdb, make sure all the services that it is

diff --git a/docs/docusaurus/versioned_docs/version-1.4.X/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.4.X/lte/dev_notes.md
@@ -161,7 +161,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 If you need to debug MME with gdb, make sure all the services that it is

diff --git a/docs/docusaurus/versioned_docs/version-1.5.X/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.5.X/lte/dev_notes.md
@@ -163,7 +163,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 If you need to debug MME with gdb, make sure all the services that it is

diff --git a/docs/docusaurus/versioned_docs/version-1.6.X/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.6.X/lte/dev_notes.md
@@ -196,7 +196,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 If you need to debug MME with gdb, make sure all the services that it is

diff --git a/docs/docusaurus/versioned_docs/version-1.6.X/lte/s1ap_tests.md b/docs/docusaurus/versioned_docs/version-1.6.X/lte/s1ap_tests.md
@@ -15,7 +15,7 @@ subscriber, APN, policy rules, etc.). If an Orc8r is connected, these configurat
 would be overwritten periodically and also lead to restart of services, both of which will
 interfere with the test scenario.
 
-TODO: Update this document once integration tests with cloud are also supported
+<!-- TODO: Update this document once integration tests with cloud are also supported -->
 
 Our VM-only tests use 3 Vagrant-managed VMs hosted on the local device (laptop):
 

diff --git a/docs/docusaurus/versioned_docs/version-1.7.0/lte/dev_notes.md b/docs/docusaurus/versioned_docs/version-1.7.0/lte/dev_notes.md
@@ -216,7 +216,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 

diff --git a/docs/docusaurus/versioned_docs/version-1.7.0/lte/s1ap_tests.md b/docs/docusaurus/versioned_docs/version-1.7.0/lte/s1ap_tests.md
@@ -16,7 +16,7 @@ subscriber, APN, policy rules, etc.). If an Orc8r is connected, these configurat
 would be overwritten periodically and also lead to restart of services, both of which will
 interfere with the test scenario.
 
-TODO: Update this document once integration tests with cloud are also supported
+<!-- TODO: Update this document once integration tests with cloud are also supported -->
 
 Our VM-only tests use 3 Vagrant-managed VMs hosted on the local device (laptop):
 

diff --git a/docs/readmes/lte/dev_notes.md b/docs/readmes/lte/dev_notes.md
@@ -215,7 +215,7 @@ as follows:
 From within the gdb shell, `bt` command will display the backtrace for the
 segmentation fault.
 
-TODO: add steps to read coredumps from python services
+<!-- TODO: add steps to read coredumps from python services -->
 
 ### Running MME with gdb
 

diff --git a/docs/readmes/lte/s1ap_tests.md b/docs/readmes/lte/s1ap_tests.md
@@ -15,7 +15,7 @@ subscriber, APN, policy rules, etc.). If an Orc8r is connected, these configurat
 would be overwritten periodically and also lead to restart of services, both of which will
 interfere with the test scenario.
 
-TODO: Update this document once integration tests with cloud are also supported
+<!-- TODO: Update this document once integration tests with cloud are also supported -->
 
 Our VM-only tests use 3 Vagrant-managed VMs hosted on the local device (laptop):