Real-time Analytics with ClickHouse: Level 2 Lab 4.1 Step 6

In the Lab 4.1 Step 6, the guide line is
e. Replace the postcode column with two low cardinality string columns for postcode1 and postcode2

The solution provided (Both in git and on the Academy) is
CREATE TABLE uk_prices_3
(
id UUID,
price UInt32,
date DateTime,
postcode1 String,
postcode2 String,
type Enum8('terraced' = 1, 'semi-detached' = 2, 'detached' = 3, 'flat' = 4, 'other' = 0),
is_new UInt8,
duration Enum8('freehold' = 1, 'leasehold' = 2, 'unknown' = 0),
addr1 String,
addr2 String,
street String,
locality LowCardinality(String),
town LowCardinality(String),
district LowCardinality(String),
county LowCardinality(String)
)
ENGINE = MergeTree
PRIMARY KEY (postcode1, postcode2);

I believe it should be
postcode1 LowCardinality(String),
postcode2 LowCardinality(String),

+ On the Academy guideline, same exercice, we have :
i. duration and addr2 are of type String

I believe it should be
i. addr1 and addr2 are of type String
as duration is handled in H as : h. duration is the following enumeration:

Regards,

Start with the Lab 4.1 Step 6 guide and Academy guideline, then compare them with the provided CREATE TABLE solution. Update the documented postcode columns and the duration/addr1/addr2 descriptions so both sources agree with the stated schema.

Written by the indexing model from the issue text.