m

Author: ajewellamz

specification/searchable-encryption/beacons.md

@@ -84,17 +84,17 @@ The beacon string will be 1/4 this length.
 
 ### Terminal Location
 
-A terminal location designates a portion of a structured value. Defined [here](virtual.md#terminal-location).
+A [terminal location](virtual.md#terminal-location) designates a portion of a structured value.
 
 ### Standard Beacon
 
 The simplest form of beacon is a standard beacon.
 
 To configure a single standard beacon, you need to provide
 
-1.  A name
-1.  A [terminal location](virtual.md#terminal-location)
-1.  A [beacon length](#beacon-length)
+1. A name
+1. A [terminal location](virtual.md#terminal-location)
+1. A [beacon length](#beacon-length)
 
 A hash is made from the value at the terminal location, and stored at
 at the top level of the structure with the name `aws_dbe_b_` followed by the configured name.
@@ -123,11 +123,11 @@ into a complex string, suitable for complex database operations.
 
 To configure a single compound beacon, you need to provide
 
-1.  A name
-1.  A split character
-1.  A list of encrypted parts
-1.  A list of signed parts
-1.  A list of constructors
+1. A name
+1. A split character
+1. A list of encrypted parts
+1. A list of signed parts
+1. A list of constructors
 
 The `name` is used in queries and index creation as if it were a regular field.
 "MyField" in examples below. It is an error if this name is the same as a configured

specification/searchable-encryption/search-config.md

@@ -405,7 +405,7 @@ while providing a Shared Cache to the [Beacon Key Source](#beacon-key-source).
 
 The resource suffixes for the Searchable Encryption is as follows:
 
-```
+```text
 logicalKeyStoreName + NULL_BYTE + UTF8Encode(branchKeyId)
 ```
 
@@ -441,7 +441,7 @@ All the above fields must be separated by a single NULL_BYTE `0x00`.
 
 As a formula:
 
-```
+```text
 resource-id = [0x02]
 scope-id = [0x03]
 logical-key-store-name = UTF8Encode(beaconVersion.keystore.LogicalKeyStoreName)