@@ -13,15 +13,15 @@ Reporting a bug
1313---------------
1414
1515The way to report bugs is to use the
16- `GitHub issue tracker <http://github.com/digidotcom/python- xbee/issues >`_.
16+ `GitHub issue tracker <http://github.com/digidotcom/xbee-python /issues >`_.
1717Before reporting a bug, please read the following points:
1818
1919#. Make sure that what you are seeing is really a bug by checking the
2020 `documentation <https://xbplib.readthedocs.io/en/latest >`_ and consulting
2121 the `FAQs <https://xbplib.readthedocs.io/en/latest/faq.html >`_ section.
2222#. If you still think you have found a bug, make sure someone has not already
2323 reported it. See the list of
24- `known issues <http://github.com/digidotcom/python- xbee/issues >`_.
24+ `known issues <http://github.com/digidotcom/xbee-python /issues >`_.
2525#. If it has not been reported yet, create a new issue. Make sure to add enough
2626 detail so that the bug can be reproduced.
2727
@@ -38,14 +38,14 @@ Suggesting a new feature
3838 section to ensure that the behavior you would like the library to have is
3939 not excluded.
4040#. Make sure someone has not already requested it. See the list of
41- `known issues <http://github.com/digidotcom/python- xbee/issues >`_.
41+ `known issues <http://github.com/digidotcom/xbee-python /issues >`_.
4242#. Submit your request in the issue tracker.
4343
4444
4545Contributing code
4646-----------------
4747
48- #. Fork the `XBee Python library <http://github.com/digidotcom/python- xbee >`_
48+ #. Fork the `XBee Python library <http://github.com/digidotcom/xbee-python >`_
4949 repository (`how to fork a repo
5050 <https://help.github.com/articles/fork-a-repo/> `_).
5151#. Create a branch for your contribution. Use a name that defines the purpose
0 commit comments