From 11564dec3b0d1e65b5b6057f1555f88657030b58 Mon Sep 17 00:00:00 2001 From: Jacob Perron Date: Tue, 26 Mar 2019 11:22:27 -0700 Subject: [PATCH] Replace the term 'subfolder' with 'subnamespace'. Signed-off-by: Jacob Perron --- articles/143_legacy_interface_definition.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/143_legacy_interface_definition.md b/articles/143_legacy_interface_definition.md index f67b3e647..6eba92c13 100644 --- a/articles/143_legacy_interface_definition.md +++ b/articles/143_legacy_interface_definition.md @@ -56,10 +56,10 @@ Each action describes three messages, one for the goal data structure, one for t Every data structure can be uniquely identified with three pieces of information: 1. **Package** - the name of the package containing the data structure definition. -2. **Subfolders** - the list of subfolders within the package where the data structure defintion can be found. +2. **Subnamespaces** - the list of namespaces within the package where the data structure is defined. 3. **Name** - the name of the data structure. -For example, a message with the name `Foo` in subfolder `msg` of the package `bar` has the unique identifier `bar/msg/Foo`. +For example, a message with the name `Foo` in the namespace `msg` of the package `bar` has the unique identifier `bar/msg/Foo`. Here, `/` is used as a separator, but in practice any delimeter could be used. ### Field types