From ec5aa2b5b932cf90d55064392a9a764588e1abe2 Mon Sep 17 00:00:00 2001 From: Nicola Corti Date: Fri, 9 Sep 2022 13:58:21 +0100 Subject: [PATCH] Fix numbered list --- docs/the-new-architecture/pillars.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/the-new-architecture/pillars.md b/docs/the-new-architecture/pillars.md index cdec1d00950..ebe05d93a05 100644 --- a/docs/the-new-architecture/pillars.md +++ b/docs/the-new-architecture/pillars.md @@ -26,9 +26,9 @@ For the sake of this guide we're going to use the following **terminology**: The next sections contain an high-level overview of the pillars, together with the steps to create them. To create one of these pillars, the steps are: 1. Define a JavaScript specification using Flow or TypeScript. -2. Configure the dependencies management system to generate code from the provided spec. -3. Implement the Native code. -4. Integrate the code in the app. +1. Configure the dependencies management system to generate code from the provided spec. +1. Implement the Native code. +1. Integrate the code in the app. Finally, we dive a little deeper into the [Codegen](pillars-codegen) process that is required to create all the C++ types and files used by our components, including some useful steps to work comfortably while developing the component.