From fd865c3d149030eec38e4ad6e082756f9a0e3975 Mon Sep 17 00:00:00 2001 From: Stefan Tatschner Date: Sat, 6 Jun 2015 22:43:07 +0200 Subject: [PATCH] device-ids: Use proper code blocks --- dev/device-ids.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/dev/device-ids.rst b/dev/device-ids.rst index 2cf87e934..20446d346 100644 --- a/dev/device-ids.rst +++ b/dev/device-ids.rst @@ -79,15 +79,17 @@ encodes five bits per character, so we need 256 / 5 = 51.2 characters to encode the device ID. This becomes 52 characters in practice, but 52 characters of base32 would decode to 260 bits which is not an whole number of bytes. The base32 encoding adds padding to 280 bits (the next multiple of both 5 and 8 -bits) so the resulting ID looks something like -``MFZWI3DBONSGYYLTMRWGC43ENRQXGZDMMFZWI3DBONSGYYLTMRWA====``. +bits) so the resulting ID looks something like:: + + MFZWI3DBONSGYYLTMRWGC43ENRQXGZDMMFZWI3DBONSGYYLTMRWA==== The padding (``====``) is stripped away, the device ID split in four groups, and `check digits `__ are added for each group. For presentation purposes the device ID is -grouped with dashes, resulting in the final value: -``MFZWI3D-BONSGYC-YLTMRWG-C43ENR5 -QXGZDMM-FZWI3DP-BONSGYY-LTMRWAD``. +grouped with dashes, resulting in the final value:: + + MFZWI3D-BONSGYC-YLTMRWG-C43ENR5 -QXGZDMM-FZWI3DP-BONSGYY-LTMRWAD Connection Establishment ~~~~~~~~~~~~~~~~~~~~~~~~