Remove references to deprecated services

.github/actions/spelling/allow.txt

@@ -137,6 +137,7 @@ datahub
 dataminer
 dataverse
 dateadded
+datetime
 davix
 dbhost
 dbpwd
@@ -215,6 +216,7 @@ flushdns
 fnal
 folksonomy
 fom
+FPGA
 fqan
 fqdns
 FZK
@@ -245,6 +247,7 @@ gpgcheck
 gpgkey
 gpgpu
 gpgpugrisu
+GPUs
 grafana
 gridftp
 gridice
@@ -341,6 +344,7 @@ kubectl
 kubernetes
 kubeserver
 labhub
+LCG
 lcgnames
 lcgpbs
 ldap
@@ -437,6 +441,7 @@ OAIS
 oauth
 occi
 ODV
+OGC
 ogf
 oidc
 oidcaccesstoken
@@ -637,6 +642,7 @@ userjdoe
 userkey
 uwsgi
 validgrid
+varchar
 vcpus
 vda
 vdb

.github/actions/spelling/patterns.txt

@@ -140,6 +140,7 @@ mailto:[-a-zA-Z=;:/?%&0-9+@.]{3,}
 \bMITREid\b
 \bIaaS\b
 \bFaaS\b
+\bPaaS\b
 \bStoRM\b
 \b.*SDPK.*\b
 \b.*HEP.*\b

content/en/users/compute/cloud-compute/gpgpu/_index.md

@@ -39,7 +39,7 @@ with your Check-In account. More information is available in the
 
 GPUs sites can be accessed in different ways: via site-specific dashboards and
 endpoints or via common federated-cloud services like the OpenStack Horizon
-dashboards, [VMOps Dashboard](../monitor), or a [cloud orchestrator](../automate).
+dashboards or a [cloud orchestrator](../automate).
 
 It is also possible to use the
 [FedCloud Client](../../../getting-started/cli) for command-line access. Below is

content/en/users/getting-started/_index.md

@@ -172,14 +172,9 @@ For pre-configured services (e.g.: [EGI Notebooks](../dev-env/notebooks/)),
 the capacity allocated includes up to **4 vCPU cores, 8 GB of RAM and
 10 GB of block storage**.
 
-You can manage those resources via [command-line](cli) or any of the dashboards
-of the EGI Cloud: the [VMOps dashboard](../compute/cloud-compute/monitor/) and
-the [IM dashboard](../compute/orchestration/im/dashboard/).
-
-You can also easily access scientific applications,
-[EC3](../compute/orchestration/ec3) has a list of
-[applications](../compute/orchestration/ec3/apps/) that you can easily start
-from the [EC3 portal](https://servproject.i3m.upv.es/ec3-ltos/index.php).
+You can manage those resources via [command-line](cli) or web interface
+like the
+[Infrastructure Manager dashboard](../compute/orchestration/im/dashboard/).
 
 ## Unused resources
 

content/en/users/getting-started/architecture/_index.md

@@ -68,17 +68,11 @@ cloud providers at three different layers:
 - Directly using the IaaS APIs or [CLIs](../cli) to manage individual resources.
   This option is recommended for preexisting use cases with requirements on
   specific APIs.
-- Using federated access tools that allow managing the complexity of dealing
-  with different providers in a uniform way. These tools include:
-  - **Provisioning systems** allow users to define infrastructure as code, then
-    manage and combine resources from different providers, thus enabling the
-    portability of application deployments between them (e.g.
-    [Infrastructure Manager](../../compute/orchestration/im) or
-    [Terraform](https://www.terraform.io/)), and
-  - **Cloud brokers** provide matchmaking for workloads to available providers
-    (e.g. the
-    [INDIGO-DataCloud Orchestrator](https://indigo-dc.gitbook.io/indigo-paas-orchestrator/)).
-- Using the [VMOps dashboard](../../compute/cloud-compute/monitor).
+- Using **Provisioning systems** allow users to define infrastructure as code,
+  then manage and combine resources from different providers, thus enabling
+  the portability of application deployments between them (e.g.
+  [Infrastructure Manager](../../compute/orchestration/im) or
+  [Terraform](https://www.terraform.io/)).
 
 EGI provides ready-to-use software components to enable the federation for
 OpenStack. These components rely on public APIs of the IaaS system and use

content/en/users/tutorials/adhoc/create-your-first-virtual-machine/_index.md

@@ -37,7 +37,7 @@ AppDB is one of the service in the
 
 Once your membership to a VO has been approved you are ready to create your first
 Virtual Machine. There are several ways to achieve this. The simplest way is to
-use a web dashboard like [VMOps Dashboard](../../../compute/cloud-compute/monitor) or
+use the
 [Infrastructure Manager Dashboard](../../../compute/orchestration/im/dashboard).
 On the other hand, advanced users
 may prefer to use the [command-line interface](../../../getting-started/cli).