Fix selective build broken links and format (#947)

Summary:
Pull Request resolved: #947

As titled.

Reviewed By: kirklandsign

Differential Revision: D50289825

fbshipit-source-id: f834a844d6ec1d4560f28ece36bdc7f0b0f384c5

Author: larryliu0820

docs/source/_static/img/kernel-library-selective_build.png renamed to docs/source/_static/img/kernel-library-selective-build.png

@@ -61,7 +61,7 @@ An open-source, cross-platform family of tools designed to build, test and packa
 
 ## Codegen
 
-In ExecuTorch, code generation is used to generate the [kernel registration library](./kernel-library-selective_build.md).
+In ExecuTorch, code generation is used to generate the [kernel registration library](./kernel-library-selective-build.md).
 
 ## [Core ATen Dialect](https://pytorch.org/docs/stable/torch.compiler_ir.html#irs)
 
@@ -271,7 +271,7 @@ The ExecuTorch runtime executes models on edge devices. It is responsible for pr
 
 Software Development Kit. The tooling users need to profile, debug and visualize programs that are running with ExecuTorch.
 
-## [Selective build](./kernel-library-selective_build.md)
+## [Selective build](./kernel-library-selective-build.md)
 
 An API used to build a leaner runtime by linking only to kernels used by the program. This provides significant binary size savings.
 

docs/source/concepts.md

@@ -81,7 +81,7 @@ Finally, the emitted program can be serialized to [flatbuffer](https://github.co
 
 With the serialized program, and provided kernel libraries (for operator calls) or backend libraries (for delegate calls), model deployment engineers can now prepare the program for the runtime.
 
-ExecuTorch has the _[selective build](./kernel-library-selective_build.md)_ APIs, to build the runtime that links to only kernels used by the program, which can provide significant binary size savings in the resulting application.
+ExecuTorch has the _[selective build](./kernel-library-selective-build.md)_ APIs, to build the runtime that links to only kernels used by the program, which can provide significant binary size savings in the resulting application.
 
 
 ## Program Execution

docs/source/getting-started-architecture.md

@@ -162,7 +162,7 @@ Topics in this section will help you get started with ExecuTorch.
 
    kernel-library-overview
    kernel-library-custom-aten-kernel
-   kernel-library-selective_build
+   kernel-library-selective-build
 
 .. toctree::
    :glob:

docs/source/index.rst

@@ -4,7 +4,7 @@ _Selective build_ is a build mode on ExecuTorch that uses model metadata to guid
 
 This document aims to help ExecuTorch users better use selective build, by listing out available APIs, providing an overview of high level architecture and showcasing examples.
 
-Preread: Overview of the ExecuTorch runtime, High-level architecture and components of ExecuTorch
+Preread: [Overview of the ExecuTorch runtime](./runtime-overview.md), [High-level architecture and components of ExecuTorch](./getting-started-architecture.md)
 
 
 ## Design Principles
@@ -13,14 +13,14 @@ Preread: Overview of the ExecuTorch runtime, High-level architecture and compone
 
 **What are we selecting?** Our core ExecuTorch library is around 50kB with no operators/kernels or delegates. If we link in kernel libraries such as the ExecuTorch in-house portable kernel library, the binary size of the whole application surges, due to unused kernels being registered into the ExecuTorch runtime. Selective build is able to apply a filter on the kernel libraries, so that only the kernels actually being used are linked, thus reducing the binary size of the application.
 
-**How do we select? **Selective build provides APIs to allow users to pass in _op info_, operator metadata derived from target models. Selective build tools will gather these op info and build a filter for all kernel libraries being linked in.
+**How do we select?** Selective build provides APIs to allow users to pass in _op info_, operator metadata derived from target models. Selective build tools will gather these op info and build a filter for all kernel libraries being linked in.
 
 
 ## High Level Architecture
 
 
 
-![](./_static/img/kernel-library-selective_build.png)
+![](./_static/img/kernel-library-selective-build.png)
 
 
 Note that all of the selective build tools are running at build-time (to be distinguished from compile-time or runtime). Therefore selective build tools only have access to static data from user input or models.
@@ -56,19 +56,14 @@ If this input is set to true, it means we are registering all the kernels from a
 
 ### Select ops from schema yaml
 
-Context: each kernel library is designed to have a yaml file associated with it. For more information on this yaml file, see here (TODO: add link to kernel library documentation). This API allows users to pass in the schema yaml for a kernel library directly, effectively allowlisting all kernels in the library to be registered.
+Context: each kernel library is designed to have a yaml file associated with it. For more information on this yaml file, see [Kernel Library Overview](./kernel-library-overview.md). This API allows users to pass in the schema yaml for a kernel library directly, effectively allowlisting all kernels in the library to be registered.
 
 
 ### Select root ops from operator list
 
 This API lets users pass in a list of operator names. Note that this API can be combined with the API above and we will create a allowlist from the union of both API inputs.
 
 
-### Select from model (WIP)
-
-This API takes a model and extracts all op info from it.
-
-
 ## Example Walkthrough
 
 

docs/source/kernel-library-selective_build.md renamed to docs/source/kernel-library-selective-build.md

@@ -58,4 +58,4 @@ et_operator_library(
 
 We then let the custom ops library depend on this target, to only register the ops we want.
 
-For more information about selective build, please refer to [`selective_build.md`](../../../docs/source/kernel-library-selective_build.md).
+For more information about selective build, please refer to [`selective_build.md`](../../../docs/source/kernel-library-selective-build.md).