From b1ff4aff02c69fc149cd5759d2f6c446f6a45ba9 Mon Sep 17 00:00:00 2001 From: songwenping Date: Wed, 2 Sep 2020 15:38:08 +0800 Subject: [PATCH] Correct spell error from `seperate` to `separate` Change-Id: I86c156e13b3648704039462570a4d9f171d6e7f8 --- .../specs/train/approved/2005473-support-consumer-types.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/specs/train/approved/2005473-support-consumer-types.rst b/doc/source/specs/train/approved/2005473-support-consumer-types.rst index d052b19ab..f2be25999 100644 --- a/doc/source/specs/train/approved/2005473-support-consumer-types.rst +++ b/doc/source/specs/train/approved/2005473-support-consumer-types.rst @@ -123,7 +123,7 @@ The placement database will get a new ``consumer_types`` table that will have a default consumer type called ``UNKNOWN`` and the ``consumers`` table will get a new ``consumer_type_id`` column that by default will point to the ``UNKNOWN`` consumer type. The migration is intended to solely be an alembic -migration although a comparision can be done for this versus having a seperate +migration although a comparision can be done for this versus having a separate online data migration to update null values to "UNKNOWN" to pick the faster one.