Update TheoryOfOperation.tex

regrant · web-flow · commit 2d02e241ed04 · 2022-03-18T12:37:21.000-04:00
diff --git a/TheoryOfOperation.tex b/TheoryOfOperation.tex
@@ -128,7 +128,7 @@ \section{System Description}\label{sec:PowerAPIBaseSysDesc}
 	All object types in this specification must be defined in any implementation. The use of the object types, with the exception of the \texttt{Platform} object type, is optional.
 	}
 	\item{
-	Objects can only have one parent but may have many children. Currently the \texttt{Facility} object has no parent as it represents the top of the system description.
+	Objects can have at most one parent but may have many children. Currently the \texttt{Facility} object has no parent as it represents the top of the system description.
 	}
         \item{
         If an implementation chooses to add objects not defined in the specification they should only be exposed to the user in a vendor specific context to avoid unpredictable or non-portable behaviour (see \funcref{CntxtInit}).

Original file line number	Diff line number	Diff line change
`@@ -128,7 +128,7 @@ \section{System Description}\label{sec:PowerAPIBaseSysDesc}`
`128`	`128`	`All object types in this specification must be defined in any implementation. The use of the object types, with the exception of the \texttt{Platform} object type, is optional.`
`129`	`129`	`}`
`130`	`130`	`\item{`
`131`		`- Objects can only have one parent but may have many children. Currently the \texttt{Facility} object has no parent as it represents the top of the system description.`
	`131`	`+ Objects can have at most one parent but may have many children. Currently the \texttt{Facility} object has no parent as it represents the top of the system description.`
`132`	`132`	`}`
`133`	`133`	`\item{`
`134`	`134`	`If an implementation chooses to add objects not defined in the specification they should only be exposed to the user in a vendor specific context to avoid unpredictable or non-portable behaviour (see \funcref{CntxtInit}).`