remove INCORRECT_STATE note from known issues; mystery solved in #1

Author: khusmann

README.md

@@ -99,14 +99,6 @@ benlink in your own project, please let me know so I can add it to this list.
 
 ## Known issues
 
-If you don't have the audio RFCOMM socket open, and try to send any data with
-`benlink.controller.RadioController.send_tnc_data`, it will immediately reply
-with a `INCORRECT_STATE` error. If you immediately retry the command within two
-seconds, it will work. I plan to add a higher-level interface for sending /
-receiving TNC data that will automatically retry failed commands and queue /
-combine message fragments. See
-[this open issue](https://github.com/khusmann/benlink/issues/1) for more info.
-
 Audio sending / receiving is a awkward because it relies on pyav for decoding /
 encoding. In the long run, I hope to make
 [Python bindings for libsbc](https://github.com/khusmann/benlink/issues/11).

src/benlink/__init__.py

@@ -92,14 +92,6 @@ async def main():
 
 # Known issues
 
-If you don't have the audio RFCOMM socket open, and try to send any data with
-`benlink.controller.RadioController.send_tnc_data`, it will immediately reply
-with a `INCORRECT_STATE` error. If you immediately retry the command within two
-seconds, it will work. I plan to add a higher-level interface for sending /
-receiving TNC data that will automatically retry failed commands and queue /
-combine message fragments. See
-[this open issue](https://github.com/khusmann/benlink/issues/1) for more info.
-
 Audio sending / receiving is a awkward because it relies on pyav for decoding /
 encoding. In the long run, I hope to make
 [Python bindings for libsbc](https://github.com/khusmann/benlink/issues/11).