[Doc][NFC] Fix typography in aircc documentation (Xilinx#301)

Author: keryell

README.md

@@ -12,4 +12,4 @@ runtimes and compilers.
 
 -----
 
-<p align="center">Copyright&copy; 2019-2022 Advanced Micro Devices, Inc.</p>
+<p align="center">Copyright&copy; 2019-2023 Advanced Micro Devices, Inc.</p>

docs/aircc.md

@@ -1,7 +1,7 @@
 # AIRCC - The AIR Compiler Driver
 
 ## Overview
-`aircc.py` is a compiler driver processing air programs. It takes the AIR MLIR
+`aircc.py` is a compiler driver processing air programs. It takes the `AIR` MLIR
 dialect as input and produces AIE binaries plus host library code as output.
 
 ## Usage
@@ -36,7 +36,7 @@ optional arguments:
 ```
 
 Python:
-```
+```Python
 import air.compiler.aircc.main as aircc
 
 # same as command line options above, but as a python list
@@ -47,31 +47,31 @@ aircc.run(air_module, aircc_options)
 
 ## Compilation pipeline
 
-aircc.py runs several code transformations and tools to generate executable
-code from AIR dialect.
+`aircc.py` runs several code transformations and tools to generate executable
+code from `AIR` dialect.
 
 The first steps are to:
-- Run herd placement (`air-place-herds`) using the aircc.py commmand line options
-- Run AIR dialect to AIR dialect conversion (`air-to-aie`)
+- Run herd placement (`air-place-herds`) using the `aircc.py` commmand line options
+- Run `AIR` dialect to `AIE` dialect conversion (`air-to-aie`)
 
-The `air-to-aie` pass will generate an AIE dialect MLIR module for each AIR
-dialect partition in the program and will add runtime metadata to the AIR
+The `air-to-aie` pass will generate an `AIE` dialect MLIR module for each `AIR`
+dialect partition in the program and will add runtime metadata to the `AIR`
 dialect program.
 
 ### Lowering of control code
 
-The AIR dialect program is lowered to control code with the following pipeline:
-- Run `air-to-std` to generate AIRRt dialect from AIR dialect.
-- Run `airrt-to-llvm` to lower AIRRt dialect to LLVM dialect
+The `AIR` dialect program is lowered to control code with the following pipeline:
+- Run `air-to-std` to generate `AIRRt` dialect from `AIR` dialect.
+- Run `airrt-to-llvm` to lower `AIRRt` dialect to `LLVM` dialect
 - Bufferize any remaing tensors
-- Lower standard dialects (linalg, scf, memref, ...) to LLVM dialect
-- Translate LLVM dialect to LLVM IR (`aie-translate`)
+- Lower standard dialects (`linalg`, `scf`, `memref`, ...) to `LLVM` dialect
+- Translate `LLVM` dialect to LLVM IR (`aie-translate`)
 - Compile LLVM IR to object code (`opt` and `clang`)
 
 ### Lowering of AIE code
 
-For each AIE dialect module generated by the `air-to-aie` pass, aircc will:
- - Run `aiecc.py` on the AIE dialect module. This generates an AIE elf file for
+For each `AIE` dialect module generated by the `air-to-aie` pass, `aircc` will:
+ - Run `aiecc.py` on the `AIE` dialect module. This generates an AIE `.elf` file for
  every core in every herd in the partition and generates C++ code to configure the
  partition at runtime (using the `-aie-generate-xaiev2` option).
  - Generate a C++ wrapper defining a namespace to hold each partition's
@@ -81,13 +81,12 @@ runtime and to user programs. An example is shown below.
 The generated C++ wrappers are compiled and linked with the controlled code
 generated by the MLIR passes into a single library. This can be a shared library
 to be loaded at runtime or a static library linked into an executable. The AIE
-elf files are not part of the generated library and must be available to load
+`.elf` files are not part of the generated library and must be available to load
 into memory at runtime.
 
-Example C++ wrapper generated by aircc.py:
-```
-namespace air {
-namespace partitions {
+Example C++ wrapper generated by `aircc.py`:
+```c++
+namespace air::partitions {
 
 // One namespace for each partition in the
 // program using the MLIR symbol names
@@ -99,4 +98,4 @@ namespace partition_1 {
 }
 
 }
-}
+```