docs: minor fix for isolate-workload-cpusets (#104)

* docs: minor fix for isolate-workload-cpusets

Signed-off-by: annecyh <anne.chew@canonical.com>

* docs: fix capitalization

Signed-off-by: annecyh <anne.chew@canonical.com>

---------

Signed-off-by: annecyh <anne.chew@canonical.com>

Author: AnneCYH

docs/how-to/index.rst

@@ -25,7 +25,7 @@ Tune performance for real-time processing:
    Modify kernel boot parameters <modify-kernel-boot-parameters>
    Configure CPUs for real-time processing <cpu-boot-configs>
    Tune IRQ affinity <tune-irq-affinity>
-   Isolating CPUs from general execution with cpusets <isolate-workload-cpusets>
+   Isolate CPUs from general execution with cpusets <isolate-workload-cpusets>
 
 
 Configure Real-time Ubuntu Core:

docs/how-to/isolate-workload-cpusets.md

@@ -208,7 +208,7 @@ Slice=custom-workload.slice
 ExecStart=/home/ubuntu/my-app
 
 ```
-The important part here is the `Slice=custom-workload.slice` which points your service to the `custom-workload.slice` that you created which has access to the isolated cpus.
+The important part here is the `Slice=custom-workload.slice` which points your service to the `custom-workload.slice` that you created which has access to the isolated CPUs.
 
 The service file should be created inside the `/etc/systemd/system` directory, for example at `/etc/systemd/system/my-app.service`.
 
@@ -278,4 +278,4 @@ In the service report, you can verify that the service is running inside the des
 
 [systemd.special]: https://manpages.ubuntu.com/manpages/noble/man7/systemd.special.7.html
 
-[systemd_slice]: https://www.freedesktop.org/software/systemd/man/latest/systemd.slice.html
+[systemd_slice]: https://www.freedesktop.org/software/systemd/man/latest/systemd.slice.html