summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrank Baker <fbaker@hdfgroup.org>1999-04-16 15:31:54 (GMT)
committerFrank Baker <fbaker@hdfgroup.org>1999-04-16 15:31:54 (GMT)
commit6adb97528250296c2f148a190597fcaa0641d51e (patch)
tree576843d5ec32159eac1d42c03a0249ee00e61131
parentde64ec3976af96151de8975184e7c36a9fd25342 (diff)
downloadhdf5-6adb97528250296c2f148a190597fcaa0641d51e.zip
hdf5-6adb97528250296c2f148a190597fcaa0641d51e.tar.gz
hdf5-6adb97528250296c2f148a190597fcaa0641d51e.tar.bz2
[svn-r1188] Attributes.html
Minor copy edits.
-rw-r--r--doc/html/Attributes.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/html/Attributes.html b/doc/html/Attributes.html
index fd917ca..b50b95a 100644
--- a/doc/html/Attributes.html
+++ b/doc/html/Attributes.html
@@ -71,10 +71,10 @@ And in this document, the
<h2>1. Introduction</h2>
- <p>The appribute API (H5A) is primarily designed to easily allow small
+ <p>The attribute API (H5A) is primarily designed to easily allow small
datasets to be attached to primary datasets as metadata information.
Additional goals for the H5A interface include keeping storage
- requirement for each attribute to a minimum and easily sharing
+ requirements for each attribute to a minimum and easily sharing
attributes among datasets.
<p>Because attributes are intended to be small objects, large datasets
intended as additional information for a primary dataset should be
@@ -83,7 +83,7 @@ And in this document, the
indicate a particular type of dataset with supplemental datasets is
located in the group. How small is "small" is not defined by the
library and is up to the user's interpretation.
- <p>Attributes are not seperate objects in the file, they are always
+ <p>Attributes are not separate objects in the file, they are always
contained in the object header of the object they are attached to. The
I/O functions defined below are required to read or write attribute
information, not the H5D I/O routines.
@@ -106,12 +106,12 @@ And in this document, the
and <em>space_id</em> are created with the H5T and H5S interfaces
respectively. Currently only simple dataspaces are allowed for attribute
dataspaces. The <em>create_plist_id</em> property list is currently
- unused, but will be used int the future for optional properties of
+ unused, but will be used in the future for optional properties of
attributes. The attribute ID returned from this function must be released
with H5Aclose or resource leaks will develop. Attempting to create an
attribute with the same name as an already existing attribute will fail,
leaving the pre-existing attribute in place.
- This function returns a attribute ID for success or negative for failure.
+ This function returns an attribute ID for success or negative for failure.
<br><br>
<dt><code>hid_t H5Aopen_name (hid_t <em>loc_id</em>, const char
@@ -120,7 +120,7 @@ And in this document, the
specified with <em>loc_id</em>. The name specified with <em>name</em>
indicates the attribute to access. The attribute ID returned from this
function must be released with H5Aclose or resource leaks will develop.
- This function returns a attribute ID for success or negative for failure.
+ This function returns an attribute ID for success or negative for failure.
<br><br>
<dt><code>hid_t H5Aopen_idx (hid_t <em>loc_id</em>, unsigned
@@ -130,7 +130,7 @@ And in this document, the
indicates the <em>idx</em>th attribute to access, starting with '0'. The
attribute ID returned from this function must be released with H5Aclose or
resource leaks will develop.
- This function returns a attribute ID for success or negative for failure.
+ This function returns an attribute ID for success or negative for failure.
<br><br>
<dt><code>herr_t H5Aclose (hid_t <em>attr_id</em>)</code>
@@ -178,7 +178,7 @@ And in this document, the
unsigned *<em>attr_number</em>,
H5A_operator <em>operator</em>,
void *<em>operator_data</em>)</code>
- <dd> This function interates over the attributes of dataset or group
+ <dd> This function iterates over the attributes of the dataset or group
specified with <em>loc_id</em>. For each attribute of the object, the
<em>operator_data</em> and some additional information (specified below)
are passed to the <em>operator</em> function. The iteration begins with