Merge pull request #11279 from NREL/cleanup-spellings

Doc, Error Message, and Comment String Spelling Corrections

Author: mitchute

doc/engineering-reference/src/simulation-models-encyclopedic-reference-004/solar-collectors.tex

@@ -979,7 +979,7 @@ \subsubsection{Heat Exchanger}\label{heat-exchanger}
 
 where \({T_{{\rm{a,HX}}}}\) is determined using correlations described above.~ When the UTSC is active, the air mass flow is determined from the operation of the outdoor air mixer component.~ When the UTSC is off, this term is zero.
 
-\subsubsection{Plenum LW Radation}\label{plenum-lw-radation}
+\subsubsection{Plenum LW Radiation}\label{plenum-lw-radation}
 
 \({q''_{LWR,plen}}\) is a standard radiation exchange formulation between the collector surface and the underlying heat transfer surface located across the plenum.~ Radiation is modeled using linearized coefficients.
 

doc/header.tex

@@ -132,7 +132,7 @@
 
 % The current implementation of \degree doesn't use ensuremath and doesn't show
 % see https://github.com/josephwright/siunitx/issues/351
-% But requried mathspec with options 'math' above fixes it
+% But required mathspec with options 'math' above fixes it
 %\DeclareSIUnit[number-unit-product = \,]
 %\degree{ \ensuremath { { } ^ { \circ } } }
 

doc/input-output-reference/src/hvac-template-objects/hvactemplate-processing.tex

@@ -11,7 +11,7 @@ \section{HVACTemplate Processing}\label{hvactemplate-processing}
 \item
   The EnergyPlus simulation proceeds using the expidf file as the input stream.
 \item
-  If there are error messages from EnergyPlus, they will refer to the contents of the expidf file. Specific objects referred to in error messages may exist in the original idf, but they may be objects created by ExpandObjects and only exist in the expidf. Remember that the expidf will be overwritten everytime the original idf is run using EP-Launch or RunEPlus.bat.
+  If there are error messages from EnergyPlus, they will refer to the contents of the expidf file. Specific objects referred to in error messages may exist in the original idf, but they may be objects created by ExpandObjects and only exist in the expidf. Remember that the expidf will be overwritten every time the original idf is run using EP-Launch or RunEPlus.bat.
 \end{enumerate}
 
 If you are trying to go beyond the capabilities of the HVACTemplate objects, one strategy you can use is to start your specification using the HVACTemplate objects, run EnergyPlus using EP-Launch and producing an expidf file, rename that file and start making modifications. This approach may help with getting all of the objects needed and the node names set consistently.

doc/input-output-reference/src/overview/group-electric-load-center-generator.tex

@@ -3649,7 +3649,7 @@ \subsubsection{Field: Heat Recovery Water Inlet Node Name}\label{field-heat-reco
 
 This field contains the node name for the water inlet to the stack cooler.
 
-\subsubsection{Field: Heat Recovery Water Outlet Node Nane}\label{field-heat-recovery-water-outlet-node-nane}
+\subsubsection{Field: Heat Recovery Water Outlet Node Name}\label{field-heat-recovery-water-outlet-node-nane}
 
 This field contains the node name for the water outlet from the stack cooler.
 

doc/input-output-reference/src/overview/group-surface-construction-elements.tex

@@ -3483,7 +3483,7 @@ \subsubsection{Inputs}\label{inputs-31-001}
 The following entries are used only if Gas Type = Custom. The A, B and C coefficients are those in the following expression that gives a property value as a function of temperature in degrees K:
 
 \begin{equation}
-Property = Coef{f_A} + Coef{f_B} \times Temperatur{e_K} + Coef{f_C} \times Temperature_K^2
+Property = Coef{f_A} + Coef{f_B} \times Temperature{e_K} + Coef{f_C} \times Temperature_K^2
 \end{equation}
 
 \paragraph{Field: Conductivity Coefficient A}\label{field-conductivity-coefficient-a-1}

doc/input-output-reference/src/weather-data/weather-data-hourly-interpolation.tex

@@ -11,7 +11,7 @@ \section{Weather Data Hourly Interpolation}\label{weather-data-hourly-interpolat
 The weighting scheme / interpolation is simply:
 
 \begin{equation}
-Valu{e_{TimeStep}} = LastHourValue\cdot Weigh{t_{LastHour}} + ThisHourValue\cdot Weigh{t_{ThisHour}}
+Value{e_{TimeStep}} = LastHourValue\cdot Weigh{t_{LastHour}} + ThisHourValue\cdot Weigh{t_{ThisHour}}
 \end{equation}
 
 where

doc/module-developer/src/appendix-b-submissions-and-check-ins.tex

@@ -30,7 +30,7 @@ \chapter{Appendix B.~ Submissions and Check-ins}\label{appendix-b.-submissions-a
 
 Shall follow the guidelines shown in this document
 
-All items shall be directly initialized (exception: derived type elements may be staticly initialized)
+All items shall be directly initialized (exception: derived type elements may be statically initialized)
 
 There shall be no ``unused'' variables.~ If you put in a variable that you ``might use later'' -- comment it out and comment it to be used later.
 
@@ -100,7 +100,7 @@ \chapter{Appendix B.~ Submissions and Check-ins}\label{appendix-b.-submissions-a
 
 ü~\textbf{FeatureChanges.csv}
 
-Every change to source code, example files, datsets, utilities (any change other than documentation) must include a line in the ``featurechanges.csv'' file.
+Every change to source code, example files, datasets, utilities (any change other than documentation) must include a line in the ``featurechanges.csv'' file.
 
 ü~\textbf{Checked in?}
 

doc/module-developer/src/energyplus-services/internal-zone-gains-services.tex

@@ -1,6 +1,6 @@
 \section{Internal Zone Gains Services}\label{internal-zone-gains-services}
 
-Services are available to help with modeling internal gains.~ Internal gains include the usual sources such as people, lights, plug loads, etc., but in EnergyPlus there can also be zone gains from the skin losses from certain equipment such as thermal tanks, electric load center equipment and refrigeration case credits.~ Developers adding new device models, or adding skin loss modeling to exisiting device models, need to use a call to SetupZoneInternalGains.~ This call is defined in DataInterfaces.f90 and contains a number of optional arguments depending on the type of internal gains involved.~ The types of gains that can be added with this call include convection, radiation, and latent gains to the zone, convection and latent gains to the return air, carbon dioxide gains to the zone and generic air contaminant gains to the zone.~ For example, the call to register gains for the People object includes convection(sensible), thermal radiation, latent, and CO2 and is:
+Services are available to help with modeling internal gains.~ Internal gains include the usual sources such as people, lights, plug loads, etc., but in EnergyPlus there can also be zone gains from the skin losses from certain equipment such as thermal tanks, electric load center equipment and refrigeration case credits.~ Developers adding new device models, or adding skin loss modeling to existing device models, need to use a call to SetupZoneInternalGains.~ This call is defined in DataInterfaces.f90 and contains a number of optional arguments depending on the type of internal gains involved.~ The types of gains that can be added with this call include convection, radiation, and latent gains to the zone, convection and latent gains to the return air, carbon dioxide gains to the zone and generic air contaminant gains to the zone.~ For example, the call to register gains for the People object includes convection(sensible), thermal radiation, latent, and CO2 and is:
 
 \textbf{CALL} SetupZoneInternalGain(People(Loop)\%ZonePtr, \&
 

doc/module-developer/src/output.tex

@@ -6,4 +6,4 @@ \chapter{Output}\label{output}
 
 OutputFileInits is intended for ``one-time'' outputs.~ If the value is calculated or entered and should be echoed to output, this file is the place for it.~ The structure is similar to the IDD/IDF structure in that there is a ``definition'' line followed by the data being reported. Since the data may be produced in several places during the simulation, the actual file looks a bit hodge-podge but can be easily imported into a spreadsheet program and grouped.
 
-OutputFileStandard is the reporting variable output file from EnergyPlus.~ You can read more details from the \href{InterfaceDeveloper.pdf}{\emph{Guide for Interface Developers}} document and in the \href{InputOutputReference.pdf}{Input Output Reference} document.~ OutputFileMeters is a similar file to contain meter (only) output.~ Meter values also may appear in the OutputFileStandard file. Only values that change during the simulation should be output to these files.~ They are automaticallly included by the SetupOutputVariable calls.
+OutputFileStandard is the reporting variable output file from EnergyPlus.~ You can read more details from the \href{InterfaceDeveloper.pdf}{\emph{Guide for Interface Developers}} document and in the \href{InputOutputReference.pdf}{Input Output Reference} document.~ OutputFileMeters is a similar file to contain meter (only) output.~ Meter values also may appear in the OutputFileStandard file. Only values that change during the simulation should be output to these files.~ They are automatically included by the SetupOutputVariable calls.

doc/output-details-and-examples/src/example-input-files.tex

@@ -6,7 +6,7 @@ \chapter{Example Input Files}\label{example-input-files}
 \item
   \textbf{ExampleFiles.xls} - lists all the files available -- whether through the install or through an external site.
 \item
-  \textbf{ExampleFiles-ObjectLink.xls} - illustrates the first 3 occurances in the example files of an object.
+  \textbf{ExampleFiles-ObjectLink.xls} - illustrates the first 3 occurrences in the example files of an object.
 \end{itemize}
 
 Following convention, each example file should have at the top a set of comments that tell what the purpose of the file is and the key features.