diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index d827438..0000000
--- a/.travis.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-language: python
-sudo: false
-python:
- - "3.8"
-install:
- - pip install -r requirements.txt
-script:
- - make html
-notifications:
-  webhooks:
-    urls:
-      - https://webhooks.gitter.im/e/2fb1c026e64fdd70d27b
-    on_success: change
-    on_failure: always
-    on_start: never
diff --git a/guide/nt.rst b/guide/nt.rst
index 612bc10..d0a4690 100644
--- a/guide/nt.rst
+++ b/guide/nt.rst
@@ -23,8 +23,8 @@ home and sometimes in the pits, it tends to not work correctly on the field at
 events. For this reason, if you use NetworkTables on the field, we strongly
 encourage teams to `ensure every device has a static IP address`.
 
-* Static IPs are ``10.XX.XX.2``
-* mDNS Hostnames are ``roborio-XXXX-frc.local`` (don't use these!)
+- Static IPs are ``10.XX.XX.2``
+- mDNS Hostnames are ``roborio-XXXX-frc.local`` (don't use these!)
 
 For example, if your team number was 1234, then the static IP to connect to
 would be  ``10.12.34.2``.
@@ -35,14 +35,10 @@ For information on configuring your RoboRIO and other devices to use static IPs,
 Resources
 ---------
 
-Installation:
+- :doc:`Networktables concepts and documentation <frc:docs/software/networktables/index>`
 
-.. seealso:: :ref:`pyntcore installation <install_pyntcore>`
+- :ref:`pyntcore installation <install_pyntcore>`
 
-API:
+- :ref:`NTCore API Reference <ntcore_api>`
 
-.. seealso:: :ref:`NTCore API Reference <ntcore_api>`
-
-Troubleshooting:
-
-.. seealso:: :ref:`NetworkTables troubleshooting <troubleshooting_nt>`
+- :ref:`NetworkTables troubleshooting <troubleshooting_nt>`
diff --git a/install/pyntcore.rst b/install/pyntcore.rst
index b9884e6..7cb369b 100644
--- a/install/pyntcore.rst
+++ b/install/pyntcore.rst
@@ -1,5 +1,6 @@
 
 .. _install_pynetworktables:
+
 .. _install_pyntcore:
 
 pyntcore install