diff --git a/doc/source/how_tos/users/agenda.rst b/doc/source/how_tos/users/agenda.rst index 025a9e66..f2090b4b 100644 --- a/doc/source/how_tos/users/agenda.rst +++ b/doc/source/how_tos/users/agenda.rst @@ -144,7 +144,7 @@ In addition to configuring the workload itself, we can also specify configuration for the underlying device which can be done by setting runtime parameters in the workload spec. Explict runtime paremeters have been exposed for configuring cpufreq, hotplug and cpuidle. For more detailed information on Runtime -Parameters see the :ref:`runtime parmeters ` section. For +Parameters see the :ref:`runtime parmeters ` section. For example, suppose we want to ensure the maximum score for our benchmarks, at the expense of power consumption so we want to set the cpufreq governor to "performance" and enable all of the cpus on the device, (assuming there are 8 diff --git a/doc/source/migration_guide.rst b/doc/source/migration_guide.rst index 650c17c5..3dc24879 100644 --- a/doc/source/migration_guide.rst +++ b/doc/source/migration_guide.rst @@ -62,7 +62,7 @@ All augmentations can now been enabled and disabled on a per workload basis. Setting Runtime Parameters ^^^^^^^^^^^^^^^^^^^^^^^^^^ -:ref:`Runtime Parameters ` are now the preferred way of +:ref:`Runtime Parameters ` are now the preferred way of configuring, cpufreq, hotplug and cpuidle rather setting the corresponding sysfile values as this will perform additional validation and ensure the nodes are set in the correct order to avoid any conflicts. diff --git a/doc/source/user_reference/runtime_parameters.rst b/doc/source/user_reference/runtime_parameters.rst index 31c1a688..7d766a9b 100644 --- a/doc/source/user_reference/runtime_parameters.rst +++ b/doc/source/user_reference/runtime_parameters.rst @@ -1,4 +1,4 @@ -.. _runtime-parmeters: +.. _runtime-parameters: Runtime Parameters ------------------