diff --git a/OGC-compliance-for-QGIS.md b/OGC-compliance-for-QGIS.md
index 70dffad..8566488 100644
--- a/OGC-compliance-for-QGIS.md
+++ b/OGC-compliance-for-QGIS.md
@@ -14,13 +14,17 @@ The certification - for each version and each service - must be renewed every ye
 
 Due to the administrative burden, QGIS.org currently only will renew certification for LTR versions.  
 
-A dedicated contact mail has been set up : `ogc at qgis dot org` forwarding mails to 3-4 persons in charge. 
 
-Régis Haubourg ([@haubourg](https://github.com/haubourg)) is currently the maintainer of the ogc certification.
+**A dedicated contact mail has been set up : `ogc at qgis dot org` forwarding mails to 3-4 persons in charge.**
+
+
+Régis Haubourg ([@haubourg](https://github.com/haubourg)) is currently the maintainer of the OGC certification.
 
 Paul Blottiere ([@pblottiere](https://github.com/pblottiere)) is managing the testing and performance infrastructure (and did most of the associated bugfixing).
 
-## Technical steps
+## Technical steps 
+
+Here follows the process for WMS service, but the process is the same for other services.
 
 1. Check that nightly test platform succeed at http://test.qgis.org/ogc_cite/wms_130/latest/report.html 
 2. Check if the reference qgis server demo is running at http://qgis4.qgis.org:8080. E. g. for 3_4 and WMS? you can check get capabilities here http://qgis4.qgis.org:8080/qgisserver_3_4_teamengine?SERVICE=WMS&REQUEST=GetCapabilities If not, ask `ogc at qgis.org` to set up a reference server for the target version
@@ -46,22 +50,25 @@ In may 2018, an official certification process has been [successful](http://www.
 
 ## Service compliance status and history
 
-| QGIS server version 	| Service 	| Service version 	| Statuts         	| certification date 	| comment                                                       	|
-|---------------------	|---------	|-----------------	|-----------------	|--------------------	|---------------------------------------------------------------	|
-| 3.0.2               	| WMS     	| 1.3.0           	| [Compliant](http://www.opengeospatial.org/resource/products/details/?pid=1496)       	| 2018-05-03         	| First official certification. Reference implementation status 	|
-| 3.4.6                 	| WMS     	| 1.3.0           	| [Compliant](http://www.opengeospatial.org/resource/products/details/?pid=1541) 	| 2019-03-08                   	|     Reference implementation status                                                     	|
-|                     	| WFS     	|                 	|                 	|                    	|                                                              	|
-
+| QGIS server version | Test endpoint | Service | Service version | Statuts | certification date | comment |  |
+|-|-|-|-|-|-|-|-|
+| 3.0.2 | http://qgis4.qgis.org:8080/qgisserver_3_4_teamengine?SERVICE=WMS | WMS | [1.3.0](https://cite.opengeospatial.org/teamengine/about/wms13/1.3.0/site/) | [Compliant](http://www.opengeospatial.org/resource/products/details/?pid=1496) | 2018-05-03 | First official certification. Reference implementation status |  |
+| 3.4.6 | http://qgis4.qgis.org:8080/qgisserver_3_4_teamengine?SERVICE=WMS | WMS | [1.3.0](https://cite.opengeospatial.org/teamengine/about/wms13/1.3.0/site/) | [Compliant](http://www.opengeospatial.org/resource/products/details/?pid=1541) | 2019-03-08 | Reference implementation status |  |
+| 3.10.10 | http://qgis4.qgis.org:8080/certification_ogcapif_qgisserver_3_10/wfs3/ | OGC APIF | [1.0](https://cite.opengeospatial.org/teamengine/about/ogcapi-features-1.0/1.0/site) | Request submitted (2020-10-05) |  |  |  |                                                            |   |
 
 ## WFS compliance
 
-A grant application in 2018 allowed to set up a permanent WFS test platform and tackle the first main issues.  
+As for 2020, we now support OGC API for Features protocol, also know as WFS3 (REST / Json style). 
 
-About 1/3 of the tests are still failing
+For older WFS, a grant application in 2018 allowed to set up a permanent WFS 1.x/2.x test platform and tackle the first main issues.  
+
+About 1/3 of the tests are still failing and need love. 
 
 ## OGC continuous integration futur plans
 
-Currently, the tests run on a separate infrastructure and failures are not forwarded in pull request in the server. Due to stability issue with TeamEngine, it was kept separated, but it would be a lot more efficient to connect the continuous integration with OGC testing. 
+~~Currently, the tests run on a separate infrastructure and failures are not forwarded in pull request in the server. Due to stability issue with TeamEngine, it was kept separated, but it would be a lot more efficient to connect the continuous integration with OGC testing.~~
+
+Since [2020-10-06](https://github.com/qgis/QGIS-Enhancement-Proposals/issues/175), certification tests are part of the integrated CI via Github Actions. See this [PR test](https://github.com/qgis/QGIS/pull/39175/checks?check_run_id=1206285984) for an example of running tests. 
 
 # Status and plans for QGIS Desktop client