Add notes

Author: jason-fox

README.ja.md

@@ -390,7 +390,7 @@ QuantumLeap のドキュメントの
 
 <a name="one-request"></a>
 
-#### :one: リクエスト :
+#### 1️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -447,7 +447,7 @@ curl -iX POST \
 
 <a name="two-request"></a>
 
-#### :two: リクエスト :
+#### 2️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -487,12 +487,12 @@ curl -iX POST \
 
 ### QuantumLeap のサブスクリプションの確認
 
-何かをする前に、:one: と :two: のステップで作成したサブスクリプションをチェックしてください (すなわち、それぞれが少なく
+何かをする前に、1️⃣ と 2️⃣ のステップで作成したサブスクリプションをチェックしてください (すなわち、それぞれが少なく
 とも 1 つの通知が送信されたか)
 
 <a name="three-request"></a>
 
-#### :three: リクエスト:
+#### 3️⃣ リクエスト:
 
 ```console
 curl -X GET \
@@ -561,7 +561,7 @@ curl -X GET \
 
 <a name="four-request"></a>
 
-#### :four: リクエスト :
+#### 4️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -599,7 +599,7 @@ curl -X GET \
 
 <a name="five-request"></a>
 
-#### :five: リクエスト :
+#### 5️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -633,7 +633,7 @@ curl -X GET \
 
 <a name="six-request"></a>
 
-#### :six: リクエスト :
+#### 6️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -675,7 +675,7 @@ curl -X GET \
 
 <a name="seven-request"></a>
 
-#### :seven: リクエスト :
+#### 7️⃣  リクエスト :
 
 ```console
 curl -X GET \
@@ -721,7 +721,7 @@ curl -X GET \
 
 <a name="eight-request"></a>
 
-#### :eight: リクエスト :
+#### 8️⃣  リクエスト :
 
 ```console
 curl -X GET \
@@ -756,7 +756,7 @@ curl -X GET \
 
 <a name="nine-request"></a>
 
-#### :nine: リクエスト :
+#### 9️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -795,7 +795,7 @@ curl -X GET \
 
 <a name="onezero-request"></a>
 
-#### :one::zero: リクエスト :
+#### 1️⃣0️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -844,7 +844,7 @@ curl -X GET \
 
 <a name="oneone-request"></a>
 
-#### :one::one: リクエスト :
+#### 1️⃣1️⃣ リクエスト :
 
 ```console
 curl -X GET \
@@ -911,7 +911,7 @@ SQL ステートメントは POST リクエストの本体として JSON 形式
 
 <a name="onetwo-request"></a>
 
-#### :one::two: リクエスト :
+#### 1️⃣2️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -945,7 +945,7 @@ curl -iX POST \
 
 <a name="onethree-request"></a>
 
-#### :one::three: リクエスト :
+#### 1️⃣3️⃣ リクエスト :
 
 ```console
 curl -X POST \
@@ -982,7 +982,7 @@ SQL 文は `ORDER BY` と `LIMIT` を使用してデータをソートします
 
 <a name="onefour-request"></a>
 
-#### :one::four: リクエスト :
+#### 1️⃣4️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -1017,7 +1017,7 @@ SQL 文は、`OFFSET` 句を使用して必要な行を取り出します。詳
 
 <a name="onefive-request"></a>
 
-#### :one::five: リクエスト :
+#### 1️⃣5️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -1053,7 +1053,7 @@ SQL 文は、最後の N 行を取り出すために `LIMIT` 節と結合され
 
 <a name="onesix-request"></a>
 
-#### :one::six: リクエスト :
+#### 1️⃣6️⃣ リクエスト :
 
 ```console
 curl -iX POST \
@@ -1090,7 +1090,7 @@ SQL 文は、`SUM` 関数と `GROUP BY` 句を使用して関連するデータ
 
 <a name="oneseven-request"></a>
 
-#### :one::seven: リクエスト :
+#### 1️⃣7️⃣  リクエスト :
 
 ```console
 curl -iX POST \
@@ -1129,7 +1129,7 @@ SQL 文は、`MIN` 関数と `GROUP BY` 句を使用して関連するデータ
 
 <a name="oneeight-request"></a>
 
-#### :one::eight: リクエスト :
+#### 1️⃣8️⃣  リクエスト :
 
 ```console
 curl -iX POST \
@@ -1168,7 +1168,7 @@ SQL 文は、`MAX`関数と `WHERE` 句を使用して関連するデータを
 
 <a name="onenine-request"></a>
 
-#### :one::nine: リクエスト :
+#### 1️⃣9️⃣ リクエスト :
 
 ```console
 curl -iX POST \

README.md

@@ -241,7 +241,8 @@ repository:
 ./services start
 ```
 
-> :information_source: **Note:** If you want to clean up and start over again you can do so with the following command:
+> [!NOTE]
+>  If you want to clean up and start over again you can do so with the following command:
 >
 > ```console
 > ./services stop
@@ -359,7 +360,7 @@ The `metadata` attribute ensures that the `time_index` column within the **Crate
 within the **MongoDB** database used by the **Orion Context Broker** rather than using the creation time of the record
 within the **CrateDB** itself.
 
-#### :one: Request:
+#### 1️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -413,7 +414,7 @@ The `metadata` attribute ensures that the `time_index` column within the **Crate
 within the **MongoDB** database used by the **Orion Context Broker** rather than using the creation time of the record
 within the **CrateDB** itself.
 
-#### :two: Request:
+#### 2️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -451,10 +452,10 @@ curl -iX POST \
 
 ### Checking Subscriptions for QuantumLeap
 
-Before anything, check the subscriptions you created in steps :one: and :two: are working (i.e., at least one
+Before anything, check the subscriptions you created in steps 1️⃣ and 2️⃣ are working (i.e., at least one
 notification for each was sent).
 
-#### :three: Request:
+#### 3️⃣ Request:
 
 ```console
 curl -X GET \
@@ -544,7 +545,7 @@ sampled `luminosity` values from `Lamp:001`.
 Note the use of `Fiware-Service` and `Fiware-ServicePath` headers. These are required only when data are pushed to orion
 using such headers (in multitenancy scenarios). Failing to align these headers will result in no data being returned.
 
-#### :four: Request:
+#### 4️⃣ Request:
 
 ```console
 curl -X GET \
@@ -571,7 +572,7 @@ curl -X GET \
 
 This example shows the fourth, fifth and sixth sampled `count` values of `Motion:001`.
 
-#### :five: Request:
+#### 5️⃣ Request:
 
 ```console
 curl -X GET \
@@ -598,7 +599,7 @@ curl -X GET \
 
 This example shows the latest three sampled `count` values from `Motion:001`.
 
-#### :six: Request:
+#### 6️⃣ Request:
 
 ```console
 curl -X GET \
@@ -633,7 +634,7 @@ curl -X GET \
   -H 'Accept: application/json'
 ```
 
-#### :seven: Request:
+#### 7️⃣  Request:
 
 ```console
 curl -X GET \
@@ -672,7 +673,7 @@ This example shows minimum `luminosity` values from `Lamp:001` over each minute.
 
 <!--lint enable no-blockquote-without-marker-->
 
-#### :eight: Request:
+#### 8️⃣  Request:
 
 ```console
 curl -X GET \
@@ -700,7 +701,7 @@ curl -X GET \
 This example shows maximum `luminosity` value of `Lamp:001` that occurred between from `2018-06-27T09:00:00` to
 `2018-06-30T23:59:59`.
 
-#### :nine: Request:
+#### 9️⃣ Request:
 
 ```console
 curl -X GET \
@@ -729,11 +730,12 @@ This example shows the latest four sampled `luminosity` values of lamps that are
 `52°33'16.9"N 13°23'55.0"E` (Bornholmer Straße 65, Berlin, Germany). If you have turned on all the lamps available on
 the device monitor page, you should be able to see data for `Lamp:001` and `Lamp:004`.
 
-> :information_source: **Note:** Geographical queries are only available starting from version `0.5` of QuantumLeap
+> [!NOTE]
+>  Geographical queries are only available starting from version `0.5` of QuantumLeap
 > which implements the full set of queries detailed in the Geographical Queries section of the
 > [NGSI v2 specification](http://fiware.github.io/specifications/ngsiv2/stable/).
 
-#### :one::zero: Request:
+#### 1️⃣0️⃣ Request:
 
 ```console
 curl -X GET \
@@ -772,11 +774,12 @@ This example shows the latest four sampled `luminosity` values of lamps that are
 at `52°33'16.9"N 13°23'55.0"E` (Bornholmer Straße 65, Berlin, Germany). Even if you have turned on all the lamps
 available on the device monitor page, you should only see data for `Lamp:001`.
 
-> :information_source: **Note:** Geographical queries are only available starting from version `0.5` of QuantumLeap
+> [!NOTE]
+>  Geographical queries are only available starting from version `0.5` of QuantumLeap
 > which implements the full set of queries detailed in the Geographical Queries section of the
 > [NGSI v2 specification](http://fiware.github.io/specifications/ngsiv2/stable/).
 
-#### :one::one: Request:
+#### 1️⃣1️⃣ Request:
 
 ```console
 curl -X GET \
@@ -835,7 +838,7 @@ team is aware.
 Another way to see if data are being persisted is to check if a `table_schema` has been created. This can be done by
 making a request to the **CrateDB** HTTP endpoint as shown:
 
-#### :one::two: Request:
+#### 1️⃣2️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -865,7 +868,7 @@ the subscription exists, and has been configured to send data to the correct loc
 **QuantumLeap** will persist data into separate tables within the **CrateDB** database based on the entity type. Table
 names are formed with the `et` prefix and the entity type name in lowercase.
 
-#### :one::three: Request:
+#### 1️⃣3️⃣ Request:
 
 ```console
 curl -X POST \
@@ -895,7 +898,7 @@ The response shows that both **Motion Sensor** data and **Smart Lamp** data are
 The SQL statement uses `ORDER BY` and `LIMIT` clauses to sort the data. More details can be found under within the
 **CrateDB** [documentation](https://crate.io/docs/crate/reference/en/latest/sql/statements/select.html)
 
-#### :one::four: Request:
+#### 1️⃣4️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -924,7 +927,7 @@ curl -iX POST \
 The SQL statement uses an `OFFSET` clause to retrieve the required rows. More details can be found under within the
 **CrateDB** [documentation](https://crate.io/docs/crate/reference/en/latest/sql/statements/select.html).
 
-#### :one::five: Request:
+#### 1️⃣5️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -954,7 +957,7 @@ The SQL statement uses an `ORDER BY ... DESC` clause combined with a `LIMIT` cla
 details can be found under within the **CrateDB**
 [documentation](https://crate.io/docs/crate/reference/en/latest/sql/statements/select.html).
 
-#### :one::six: Request:
+#### 1️⃣6️⃣ Request:
 
 ```console
 curl -iX POST \
@@ -985,7 +988,7 @@ of
 [Date-Time Functions](https://crate.io/docs/crate/reference/en/latest/general/builtins/scalar.html#date-and-time-functions)
 to truncate and convert the timestamps into data which can be grouped.
 
-#### :one::seven: Request:
+#### 1️⃣7️⃣  Request:
 
 ```console
 curl -iX POST \
@@ -1018,7 +1021,7 @@ of
 [Date-Time Functions](https://crate.io/docs/crate/reference/en/latest/general/builtins/scalar.html#date-and-time-functions)
 to truncate and convert the timestamps into data which can be grouped.
 
-#### :one::eight: Request:
+#### 1️⃣8️⃣  Request:
 
 ```console
 curl -iX POST \
@@ -1050,7 +1053,7 @@ The SQL statement uses a `MAX` function and a `WHERE` clause to retrieve the rel
 of [Aggregate Functions](https://crate.io/docs/crate/reference/en/latest/general/dql/selects.html#data-aggregation) to
 aggregate data in different ways.
 
-#### :one::nine: Request:
+#### 1️⃣9️⃣ Request:
 
 ```console
 curl -iX POST \