Fix urls to docs

docs/advanced.json.md

@@ -1,5 +1,5 @@
 This doc is a bit outdated, although it is still a good source of examples.
-Full description of all properties supported can be found [here](https://icpc.io/live-v3/cds/core/org.icpclive.cds.tunning/-advanced-properties/index.html)
+Full description of all properties supported can be found [here](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.tunning/-advanced-properties/index.html)
 
 # How to setup advanced.json
 
@@ -110,7 +110,7 @@ Typical awards setup includes only medals, and can be done like this
 ```
 
 More different types of awards are supported for cds-converter. 
-Check [full awards settings doc](https://icpc.io/live-v3/cds/core/org.icpclive.cds.api/-awards-settings/index.html) for details.
+Check [full awards settings doc](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.api/-awards-settings/index.html) for details.
 
 # Change problem info
 ## Color

docs/ccs-requirements.md

@@ -19,7 +19,7 @@ To support your contest system in icpc-live, we would need to provide an API wit
 * Contest name
 * Contest logos
 * Awards distribution description
-* Everything else supported [here](https://icpc.io/live-v3/cds/core/org.icpclive.cds.api/-contest-info/index.html)
+* Everything else supported [here](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.api/-contest-info/index.html)
 
 # Information about problems
 ### Must have:
@@ -42,7 +42,7 @@ To support your contest system in icpc-live, we would need to provide an API wit
 * Official team name
 * Link to team photos/screen/webcam/etc
 * University/ICPC region/other reasonable grouping
-* Everything else supported [here](https://icpc.io/live-v3/cds/core/org.icpclive.cds.api/-team-info/index.html)
+* Everything else supported [here](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.api/-team-info/index.html)
 
 # Information about runs
 ### Must-have

docs/settings.md

@@ -16,7 +16,7 @@ Also, it sometimes contains some abilities to modify received data.
 
 You can use [json schema file](https://github.com/icpc/live-v3/tree/main/schemas/settings.schema.json) in your text editor to get help with writing config. 
 
-[Here](https://icpc.io/live-v3/cds/core/org.icpclive.cds.settings/-c-d-s-settings/index.html) 
+[Here](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.settings/-c-d-s-settings/index.html) 
 is the full list of supported properties for all systems.
 
 Typical config should look like that
@@ -46,7 +46,7 @@ Whenever you need to put some url in config, you can put it in several ways:
 * As just a string. Then it would be interpreted as url, if it starts with `http://` or `https://`,
   otherwise, it would be interpreted as local file, which is useful for testing.
 * As an object with url, login, and password
-* As an object with url and full [auth](https://icpc.io/live-v3/cds/core/org.icpclive.cds.settings/-auth/index.html) object.
+* As an object with url and full [auth](https://icpc.io/live-v3/cds/cds/core/org.icpclive.cds.settings/-auth/index.html) object.
 
 A separate creds file is needed to avoid accidental publishing of your keys. 
 If you don't plan to publish a config file, you can just put the key into it instead of a separate file.