Fixed minor formatting in docs

[AlexColello]

I wanted to fix a minor issue in the docs where a code block in a comment did not completely enclose the sample code. Along the way I also ended up dealing with an issue where PyLint found too many duplicate lines of code between clue_ams_remote.py and clue_ams_remote_advanced.py.

[kattni]

Thanks for catching the docs issue! And thank you for noticing that Pylint was not running on the subfolders. I believe you may have caught something we need to fix on a few other repos as well.

Please see the suggested change below for how to update the build.yml file.

[kattni]

Please try the following instead of creating a new line to check the examples subfolder. It worked for me locally, but I would appreciate it if you could test it as well.

Suggested change

	([[ ! -d "examples" ]] || pylint --disable=missing-docstring,invalid-name,bad-whitespace $( find . -name "advanced_examples" -prune -false -o -path "./examples/*.py" ))
	([[ ! -d "examples/advanced_examples" ]] || pylint --disable=missing-docstring,invalid-name,bad-whitespace $( find . -path "./examples/advanced_examples/*.py" ))
	([[ ! -d "examples" ]] || pylint --disable=missing-docstring,invalid-name,bad-whitespace $( find examples -name \*.py ))

[AlexColello]

I tested that change in AlexColello@3f957cb, but it causes the same error as in 91674a1. I checked the find command and both this and the original produce the same results, so I don't think that is the issue.

[AlexColello]

It looks like there is some change in behavior with PyLint version 2.7.0 that is causing the error. I am not sure which behavior is absolutely correct, but for the scope of this request, keeping it at the older version seems best.

[kattni]

@AlexColello Good catch, you are correct. This issue was reported by someone else as well. However, I'm pretty sure you're also correct that it's not linting the subfolders - I tested it on another repo with subfolders in examples, and it didn't seem to catch an issue present in a subfoldered example. Please sit tight and I'm going to look into the Pylint update issue tomorrow. Thank you for your patience.

[AlexColello]

@kattni I see, that probably means that 2.7 fixed an issue that was hiding the linting errors. Here is the new error for reference

************* Module clue_ble_color_patchwork
examples/clue_ble_color_patchwork.py:1:0: R0801: Similar lines in 2 files
==clue_ams_remote:20
==clue_ams_remote_advanced:28
radio = adafruit_ble.BLERadio()  # pylint: disable=no-member
a = SolicitServicesAdvertisement()
a.solicited_services.append(AppleMediaService)
radio.start_advertising(a)

while not radio.connected:
    pass

print("connected")

known_notifications = set()

i = 0
if radio.connected:
    for connection in radio.connections:
        if not connection.paired:
            connection.pair()
            print("paired")

        ams = connection[AppleMediaService]
 (duplicate-code)
examples/clue_ble_color_patchwork.py:1:0: R0801: Similar lines in 2 files
==clue_ams_remote:49
==clue_ams_remote_advanced:120
        if clue.touch_0:
            ams.previous_track()
            time.sleep(0.25)

        # Capacitive touch pad marked 1 toggles pause/play
        if clue.touch_1:
            ams.toggle_play_pause()
            time.sleep(0.25)

        # Capacitive touch pad marked 2 advances to the next track
        if clue.touch_2:
            ams.next_track()
            time.sleep(0.25)

        # If button B (on the right) is pressed, it increases the volume
        if "B" in clue.were_pressed:
            ams.volume_up() (duplicate-code)
examples/clue_ble_color_patchwork.py:1:0: R0801: Similar lines in 2 files
==clue_ams_remote:67
==clue_ams_remote_advanced:139
        while "B" in clue.were_pressed:
            ams.volume_up()
            time.sleep(0.07)

    # If button A (on the left) is pressed, the volume decreases
    if "A" in clue.were_pressed:
        ams.volume_down() (duplicate-code)

[kattni]

That is correct, @AlexColello. I am currently working on our solution. I'll get back to you soon.

[kattni]

@AlexColello My apologies for letting this slide. We sorted out a solution for the issue. If you want to submit a new PR with the documentation change, it will run with the new Pylint setup and should pass. Again, I'm sorry for neglecting this PR.

[AlexColello]

@kattni I submitted a new PR at #40