diff --git a/docs/README.md b/docs/README.md index a7f0ca47..c4224437 100644 --- a/docs/README.md +++ b/docs/README.md @@ -44,7 +44,7 @@ helm pull {replace by the name of the chart} --version --version {replace by the In addition to the README provided in each Helm chart, the [Documentation](.) directory provides several guidelines for different implementations: - [Setup Free5GC and test with UERANSIM](demo/Setup-free5gc-and-test-with-UERANSIM.md) - [Setup free5gc on multiple clusters and test with UERANSIM](demo/Setup-free5gc-on-multiple-clusters-and-test-with-UERANSIM.md) - - [Setup free5gc on multiple clusters with a Kubernetes service to expose the AMF NGAP service and test with UERANSIM](demo/Setup-free5gc-with-a-Kubernetes-service-to-expose-the-AMF-NGAP-service-and-test-with-UERANSIM.md) + - [Setup free5gc on multiple clusters with ULCL mode and test with UERANSIM](demo/Setup-free5gc-on-multiple-clusters-with-ULCL-mode-and-test-with-UERANSIM.md) diff --git a/docs/demo/Setup-free5gc-and-test-with-UERANSIM.md b/docs/demo/Setup-free5gc-and-test-with-UERANSIM.md index 119c8e4a..3fb6dbf1 100644 --- a/docs/demo/Setup-free5gc-and-test-with-UERANSIM.md +++ b/docs/demo/Setup-free5gc-and-test-with-UERANSIM.md @@ -6,7 +6,7 @@ This guideline shows how to deploy the free5gc on a Kubernetes cluster and then ## Prerequisites - A Kubernetes cluster supporting SCTP - - Kubernetrs worker nodes with kernel 5.0.0-23-generic and containing gtp5g kernel module ([required for the Free5GC UPF element](https://github.com/free5gc/free5gc/wiki/Installation#a-prerequisites)). + - Kubernetes worker nodes with kernel 5.0.0-23-generic and containing gtp5g kernel module ([required for the Free5GC UPF element](https://github.com/free5gc/free5gc/wiki/Installation#a-prerequisites)). - [Multus-CNI](https://github.com/intel/multus-cni). - [Helm3](https://helm.sh/docs/intro/install/). - [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) (optional). @@ -14,7 +14,7 @@ This guideline shows how to deploy the free5gc on a Kubernetes cluster and then - A physical network interface on each Kubernetes node named eth0. - A physical network interface on each Kubernetes node named eth1 to connect the UPF to the Data Network. -Note: If the names of network interfaces on your Kubernetes nodes are different from eth0 and eth1, see Networks configuration. + **Note:** If the names of network interfaces on your Kubernetes nodes are different from `eth0` and `eth1`, see [Networks configuration](#networks-configuration). ## Networks configuration