Skip to content

Commit ef30b32

Browse files
ericsandurazvand
authored andcommitted
feat(guides): Fix linter errors in "Porting Advanced Applications to Unikraft"
Signed-off-by: Eric Sandu <eric_andrei.sandu@stud.acs.upb.ro>
1 parent de212e6 commit ef30b32

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

content/guides/advanced-porting.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Today, we will learn how to properly port a more complex application, using mult
1010

1111
We will use [`iperf3`](https://github.com/esnet/iperf/tree/master) as an example, a network benchmarking tool.
1212

13-
### The Unikraft Build Lifecycle
13+
## The Unikraft Build Lifecycle
1414

1515
The lifecycle of the construction of a Unikraft unikernel includes several distinct steps:
1616

@@ -404,6 +404,7 @@ As such, if you update the library or application's code (i.e. by updating, for
404404
To make a patch:
405405

406406
1. First, ensure that the remote origin code has been downloaded to the application's `build/` folder:
407+
407408
```console
408409
cd ~/workspace/apps/iperf3
409410
make fetch

0 commit comments

Comments
 (0)