Fix typos for 'beginning'.

doc/html/hdf5_profile_user_guide.shtml

@@ -262,7 +262,7 @@ Also appropriately set EnergyIPMIFrequency in acct_gather.conf.</p>
 <DD>Time of day at which the data sample was taken. This can be used to
 correlate activity with other sources such as logs.</DD></DT>
 <DT><B>Time</B>
-<DD>Elapsed time since the begining of the step.</DD></DT>
+<DD>Elapsed time since the beginning of the step.</DD></DT>
 <DT><B>Power</B>
 <DD>Power consumption during the interval.</DD></DT>
 <DT><B>CPU Frequency</B>
@@ -281,7 +281,7 @@ or in --acctg-freq on the command line.</p>
 <DD>Time of day at which the data sample was taken. This can be used to
 correlate activity with other sources such as logs.</DD></DT>
 <DT><B>Time</B>
-<DD>Elapsed time since the begining of the step.</DD></DT>
+<DD>Elapsed time since the beginning of the step.</DD></DT>
 <DT><B>Reads</B>
 <DD>Number of read operations.</DD></DT>
 <DT><B>Megabytes Read</B>
@@ -304,7 +304,7 @@ data items.</p>
 <DD>Time of day at which the data sample was taken. This can be used to
 correlate activity with other sources such as logs.</DD></DT>
 <DT><B>Time</B>
-<DD>Elapsed time since the begining of the step.</DD></DT>
+<DD>Elapsed time since the beginning of the step.</DD></DT>
 <DT><B>Packets In</B>
 <DD>Number of packets coming in.</DD></DT>
 <DT><B>Megabytes Read</B>
@@ -327,7 +327,7 @@ items.</p>
 <DD>Time of day at which the data sample was taken. This can be used to
 correlate activity with other sources such as logs.</DD></DT>
 <DT><B>Time</B>
-<DD>Elapsed time since the begining of the step.</DD></DT>
+<DD>Elapsed time since the beginning of the step.</DD></DT>
 <DT><B>CPU Frequency</B>
 <DD>CPU Frequency at time of sample.</DD></DT>
 <DT><B>CPU Time</B>

doc/html/selectplugins.shtml

@@ -609,7 +609,7 @@ the job step.</p>
 <span class="commandline"> step_ptr</span>&nbsp; &nbsp;&nbsp;(input)
 Pointer to the step which has completed execution.<br>
 <span class="commandline"> killing_step</span>&nbsp; &nbsp;&nbsp;(input)
-True if we are begining the termination of the step (for example, when SIGKILL is being sent);
+True if we are beginning the termination of the step (for example, when SIGKILL is being sent);
 False if the termination of the step has completed (all processes have exited).</p>
 <p style="margin-left:.2in"><b>Returns</b>: SLURM_SUCCESS if successful. On failure,
 the plugin should return SLURM_ERROR.</p>