spelling fix

This commit is contained in:
2026-07-20 14:53:40 +10:00
parent 7392798ec9
commit 6cc14a9894
+1 -1
View File
@@ -189,7 +189,7 @@
<div> <div>
<span class="section-label">Why we built RTOSure</span> <span class="section-label">Why we built RTOSure</span>
<h2 class="section-heading">Compliance software that actually knows your Standards.</h2> <h2 class="section-heading">Compliance software that actually knows your Standards.</h2>
<p style="font-size:16px;color:var(--color-slate);line-height:1.7;margin-bottom:var(--space-lg);">We have been working with CRICOS, ELICOS and VET Colleges since 1997. Originally helped to build CMS and eMinerva. In 2003 we launched our own SMS called TEAMS. In 2025 when NVR standards launched, a lot of our clients wanted our help with making sure they could be compliant in a systematic manner. We have been building RTO Sure and it's other variants since 2025. What you have in front of you is a culmiation of all our efforts.</p> <p style="font-size:16px;color:var(--color-slate);line-height:1.7;margin-bottom:var(--space-lg);">We have been working with CRICOS, ELICOS and VET Colleges since 1997. Originally helped to build CMS and eMinerva. In 2003 we launched our own SMS called TEAMS. In 2025 when NVR standards launched, a lot of our clients wanted our help with making sure they could be compliant in a systematic manner. We have been building RTO Sure and it's other variants since 2025. What you have in front of you is a culmination of all our efforts.</p>
<p style="font-size:16px;color:var(--color-slate);line-height:1.7;margin-bottom:var(--space-lg);">The result is a system that knows the NVR Standards 2025, the ESOS framework, the National Code 2018, and the ELICOS Standards 2018 — not as configuration options, but as the architectural foundation of the product itself.</p> <p style="font-size:16px;color:var(--color-slate);line-height:1.7;margin-bottom:var(--space-lg);">The result is a system that knows the NVR Standards 2025, the ESOS framework, the National Code 2018, and the ELICOS Standards 2018 — not as configuration options, but as the architectural foundation of the product itself.</p>
<p style="font-size:16px;color:var(--color-slate);line-height:1.7;">We're based in Australia, working exclusively in the VET and ELICOS sector. This isn't a generic compliance tool adapted for RTOs. It was built for RTOs from day one.</p> <p style="font-size:16px;color:var(--color-slate);line-height:1.7;">We're based in Australia, working exclusively in the VET and ELICOS sector. This isn't a generic compliance tool adapted for RTOs. It was built for RTOs from day one.</p>
</div> </div>