Replace references to https://eosc-portal.eu/

content/en/providers/joining/federated-resource-centre/_index.md

@@ -11,7 +11,7 @@
 Federation. It can be either localised or geographically distributed and
 provides a minimum set of local or remote IT Services compliant with
 well-defined IT Capabilities (HTC, Cloud, Storage, etc.) necessary to make
 resources accessible to Users. EGI is a Resource Infrastructure federating RCs
 to constitute a homogeneous operational domain.
 
 ## Registration and certification
@@ -24,7 +24,7 @@
 the Research Infrastructure Provider (RP) existing in its country. A RP is a
 legal organisation, part of the EGI Resource Infrastructure, responsible for
 managing and operating a number of operational services at national level,
 supporting EGI RCs and user communities. Please have a look at the
 [Operations Start Guide](../../operations-manuals/operations-start-guide/) to get familiar with the
 terms mentioned above, and to have a complete picture of the several actors
 participating in our landscape.
@@ -86,7 +86,7 @@
 
 The response time is defined by the Quality of
 [Support levels](https://confluence.egi.eu/display/EGISLM/Service+Level+Target+-+Quality+of+Support),
 and for the RCs the level will be Medium, meaning that there will 4 priorities
 for the incidents (requiring for example up to 5 working days for the “less
 urgent” tickets and up to 1 working day for the “top priority” ones), while any
 service request will be processed as “less urgent” ticket.
@@ -181,8 +181,7 @@
 - The EGI site where they can
   [request access to services](https://www.egi.eu/services/research/).
 - The [EGI-ACE Call for Use Cases](https://www.egi.eu/egi-ace-open-call/).
-- The [Marketplace](https://marketplace.eosc-portal.eu/) of the European Open
-  Science Cloud.
+- The [European Open Science Cloud](https://open-science-cloud.ec.europa.eu/).
 
 ### Service and Operation Level Agreements (SLAs, OLAs)
 

content/en/users/compute/orchestration/workload-manager/_index.md

@@ -75,9 +75,9 @@
 
 The EGI Workload Manager service is a cluster of DIRAC services running on EGI
 resources (HTC, Cloud, HPC) supporting multi-VO. All the DIRAC services are at
 or above TRL8. The main service components include:
 
 - Workload Management System (WMS) architecture is composed of multiple loosely
   coupled components working together in a collaborative manner with the help of
   a common Configuration Services ensuring reliable service discovery
   functionality. The modular architecture allows to easily incorporate new types
@@ -107,25 +107,14 @@
    service, or use [DIRAC Client](#the-dirac-client-tool).
 1. Individual researchers who want to do some number crunching for a limited
    period of time, with a reasonable (not too high) number of CPUs can use the
-   catch-all VO resource pool (`vo.access.egi.eu`). Submit a request through the
-   [EOSC Marketplace](https://marketplace.eosc-portal.eu/services/egi-workload-manager).
+   catch-all VO resource pool (`vo.access.egi.eu`).
+   [Contact us](https://www.egi.eu/service/workload-manager/).
 1. Representatives of a community who want to try DIRAC and EGI > Same as #2.
 1. Representative of a community who wants to request DIRAC for the community's
-   own resource pool > Submit a request through the
-   [EOSC Marketplace](https://marketplace.eosc-portal.eu/services/egi-workload-manager).
+   own resource pool > Same as #2.
 
 ## Getting Started
 
-### Submit a service order via the Marketplace
-
-User can request access to the service submitting a service-order to use the EGI
-HTC service directly from the EOSC Marketplace:
-
-- [EOSC Marketplace: Workload Manager](https://marketplace.eosc-portal.eu/services/egi-workload-manager)
-
-Service orders are usually handled within 5 working days by the EGI User Support
-Team on shift.
-
 ### Before starting
 
 #### Apply for your user credentials
@@ -157,7 +146,7 @@
 `dirac-support` `<AT>` `mailman.egi.eu`
 
 ```shell
 $ openssl x509 -in $HOME/.globus/usercert.pem -subject -noout
 ```
 
 ### The EGI Workload Manager Web Portal
@@ -185,7 +174,7 @@
 
 Before submitting your job, you need to upload your Proxy. Login to the portal.
 Go to:\
 `Menu` > `Tools` > `Proxy Upload`, enter your certificates .p12 file and the passphrase,
 click `Upload`.
 
 ![The wizard to upload the .p12 proxy certificate](./proxy_cert_upload_1.png)
@@ -202,7 +191,7 @@
 In the Job Launchpad, you can select your jobs from the list; add parameters,
 indicating the output Sandbox location.
 
 Now, select `Helloworld` from the job list, and click `Submit`, you just launch
 your very first job to the EGI HTC cluster.
 
 ![Submit a job with the Job Launchpad](job_submit.png)
@@ -263,7 +252,7 @@
 Manager service:
 
 ```shell
 $ dirac-configure defaults-egi.cfg Executing:
 /home/jdoe/DIRAC/DIRAC/Core/scripts/dirac-configure.py defaults-egi.cfg
 
 
@@ -282,7 +271,7 @@
 project.
 
 ```shell
 $ dirac-proxy-init --debug --group wenmr_user -U --rfc
 $ dirac-proxy-init --debug --group wenmr_user -U --rfc
 Generating proxy...
 Enter Certificate password:

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

@@ -11,7 +11,7 @@ EGI and the Pangeo community in Europe have forged
 [a collaboration](https://www.egi.eu/case-study/pangeo/)
 to provide deployments of the Pangeo ecosystem using the computing
 resources offered by the European Open Science Cloud
-([EOSC](https://eosc-portal.eu/about)). Read on to learn more about
+([EOSC](https://open-science-cloud.ec.europa.eu/)). Read on to learn more about
 how to get involved.
 
 ## About the Pangeo community in Europe