From 87112d6acaf47333b80a3b56c0d6949ae6f1b370 Mon Sep 17 00:00:00 2001 From: Filip Date: Tue, 29 Jun 2021 21:23:39 +0000 Subject: [PATCH] Consistent soong namescape example Test: not required - documentation change Change-Id: Ib487278e7ca183fd968df70fb701a8cdf7266c19 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b7e93f431..10ddd73e5 100644 --- a/README.md +++ b/README.md @@ -213,8 +213,8 @@ has empty name. A module name's **scope** is the smallest namespace containing it. Suppose a source tree has `device/my` and `device/my/display` namespaces. If `libfoo` -module is defined in `device/co/display/lib/Android.bp`, its namespace is -`device/co/display`. +module is defined in `device/my/display/lib/Android.bp`, its namespace is +`device/my/display`. The name uniqueness thus means that module's name is unique within its scope. In other words, "//_scope_:_name_" is globally unique module reference, e.g,