Skip to content

Commit 33fa8b9

Browse files
committed
Fix more typos, better variable name.
1 parent 5f212d2 commit 33fa8b9

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

jsonschema-hyperschema.xml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -933,7 +933,7 @@
933933
All three keywords share the same algorithm for resolving variables from
934934
instance data, which makes use of the "templatePointers" and "templateRequired"
935935
keywords. When resolving "href", both it and any "base" templates
936-
needed for resolution to an absolute URI, the algorithm is modfied to
936+
needed for resolution to an absolute URI, the algorithm is modified to
937937
optionally accept user input based on the "hrefSchema" keyword.
938938
</t>
939939
<t>
@@ -973,15 +973,15 @@
973973
<preamble>
974974
This is the high-level algorithm as pseudocode. "T" comes from either
975975
"href" or "anchor" within the LDO, or from "base" in a containing schema.
976-
Pseudocode for each step follows. "anchorOrHref" indicates which of the
977-
two started the process (since "base" is always resolved in order to finish
978-
resolving one or the other of those keywords).
976+
Pseudocode for each step follows. "initialTemplateKeyword" indicates
977+
which of the two started the process (since "base" is always resolved
978+
in order to finish resolving one or the other of those keywords).
979979
</preamble>
980980
<artwork>
981981
<![CDATA[
982982
templateData = populateDataFromInstance(T, ldo, instance)
983983
984-
if anchorOrHref == "href" and ldo.hrefSchema exists:
984+
if initialTemplateKeyword == "href" and ldo.hrefSchema exists:
985985
inputData = acceptInput(ldo, instance, templateData)
986986
for varname in inputData:
987987
templateData[varname] = inputData[varname]
@@ -1006,7 +1006,7 @@ R = rfc6570ResolutionAlgorithm(T, templateData)
10061006
appears in that keyword's value
10071007
</t>
10081008
<t>
1009-
Otherwise, look for a property names matching the variable in
1009+
Otherwise, look for a property name matching the variable in
10101010
the instance location to which the link is attached
10111011
</t>
10121012
<t>
@@ -1062,7 +1062,7 @@ for varname in T:
10621062
<preamble>
10631063
"InputForm" represents whatevers sort of input mechanism is appropriate.
10641064
This may be a literal web form, or may be a more programmatic construct
1065-
such as a callback funciton accepting specific fields and data types,
1065+
such as a callback function accepting specific fields and data types,
10661066
with the given initial values, if any.
10671067
</preamble>
10681068
<artwork>

0 commit comments

Comments
 (0)