diff --git a/js-apps/frontend/src/js/containers/home/home-page-container.js b/js-apps/frontend/src/js/containers/home/home-page-container.js index a6053f6cd8130dc2358b9660e035347b04810ad6..d56373b22b7a4039019329799529ab49cc551172 100644 --- a/js-apps/frontend/src/js/containers/home/home-page-container.js +++ b/js-apps/frontend/src/js/containers/home/home-page-container.js @@ -70,9 +70,10 @@ class HomePageContainer extends Component { MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behaviour and capabilities of the Location (MEC013), Radio Network - Information (MEC012), Traffic Management APIs (MEC015), Device Application Interface (MEC016), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and - Application Mobility (MEC021) service APIs. Such contextual information can offer - significant differential performance for edge based MEC applications. + Information (MEC012), Traffic Management APIs (MEC015), Application Mobility (MEC021), WLAN Information (MEC028) and + V2X Information API (MEC030) service APIs. Such contextual information can offer significant differential performance + for edge based MEC applications. + MEC Sandbox also provides the support of capabilities described by Edge Platform Application Enablement (MEC011) and Device Application Interface (MEC016).
But wait - MEC Sandbox is not only a browser experience!