fix: build warnings, broken link
All checks were successful
ci / build_and_publish (push) Successful in 2m24s

This commit is contained in:
Iain Learmonth 2026-05-27 15:48:30 +01:00
parent 0d6676a154
commit c4aa78a76b
3 changed files with 4 additions and 7 deletions

View file

@ -16,7 +16,7 @@ Our devices are provisioned with UK mobile numbers (+44 country code) however yo
provide any branding you would like to have set up.
Additional channels will be subject to a fee to cover the additional cost of each required mobile device.
If for any reason you choose to move away from our hosted platform in the future, see [Moving Away](./moving_away) for
If for any reason you choose to move away from our hosted platform in the future, see [Moving Away](../moving_away) for
details on porting your number to your new provider.
## Self-Managed Devices

View file

@ -20,7 +20,4 @@ special software or technical knowledge.
<figure style={{"text-align": "center"}}>
<img src="/img/mirrors/overview.png" style={{"max-width": "100%", "max-height": "500px"}} />
<figcaption style={{"font-weight": "bold"}}>
The jasima.app portal overview for web mirrors
</figcaption>
</figure>

View file

@ -26,7 +26,7 @@ users.
If this is not possible, then deploying mirrors for websites hosted on CDNs will require either configuration at, or
co-operation from, the CDN provider.
Additional headers can be configured for the origin to authenticate requests that originate from jasima.app, and these
Additional headers can be configured for the origin to authenticate requests that originate from the mirrors, and these
can be used to bypass the protection mechanisms at your CDN.
Consult your CDN's documentation or contact their support team to configure using an additional header to disable the
rate limiting for requests originating from jasima.app.
rate limiting for requests originating from the mirrors.