Commit 60e8de02 authored by Kevin Di Lallo's avatar Kevin Di Lallo
Browse files

doc build issue fix

parent 3dc057b9
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
@@ -33,7 +33,7 @@ The scenario includes:
- 3 terminals with pre-defined routes to move interchangeably from _mep1_ to _mep2_

**NOTE:** To view terminal movement on a map, you must first provision maps in AdvantEDGE as described
[here]({{site.baseurl}}{% link docs/overview/features/gis/overview-gis.md %}#map-provisioning)
[here]({{site.baseurl}}{% link docs/overview/features/overview-gis.md %}#map-provisioning)

### Demo server
Demo server is a web server that interacts with the _Application Enablement_ & _Application Mobility_ services
@@ -90,7 +90,7 @@ cd ~/AdvantEDGE/examples/demo3
### Deploy Demo3 scenario
After building & dockerizing the Demo3 application, the Demo3 scenario must be imported in AdvantEDGE and deployed within a sandbox.

**IMPORTANT NOTE:** For the API calls to work correctly, the platform IP address or domain name must be properly configured in the [AdvantEDGE deployment configuration]({{site.baseurl}}{% link docs/platform-mgmt/mgmt-cheat-sheet.md %}#deployment-configuration) file.
_**IMPORTANT NOTE:** For the API calls to work correctly, the platform IP address or domain name must be properly configured in the [AdvantEDGE deployment configuration]({{site.baseurl}}{% link docs/platform-mgmt/mgmt-cheat-sheet.md %}#deployment-configuration) file._

### Start Demo3 application frontend
After deploying the Demo3 scenario, the Demo3 application frontend can be accessed as follows: