[arrayfire] 01/61: Fixed typos in documentation.

[Ghislain Vaillant]

This is an automated email from the git hooks/post-receive script.

ghisvail-guest pushed a commit to branch dfsg-clean
in repository arrayfire.

commit f10075b694bb41a9bb3e270160360ccd50d6259a
Author: Miguel Lloreda <mlloreda at users.noreply.github.com>
Date:   Fri Nov 13 13:43:07 2015 -0500

    Fixed typos in documentation.
---
 docs/pages/getting_started.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/pages/getting_started.md b/docs/pages/getting_started.md
index 6d1c7cd..c1ae05e 100644
--- a/docs/pages/getting_started.md
+++ b/docs/pages/getting_started.md
@@ -22,7 +22,7 @@ underlying data may be one of various [basic types](\ref af::af_dtype):
 
 Older devices may not support double precision operations.
 
-# Creating an populating an ArrayFire array {#getting_started_af_arrays}
+# Creating and populating an ArrayFire array {#getting_started_af_arrays}
 
 ArrayFire [array](\ref af::array)s always exist on the device. They
 may be populated with data using an ArrayFire function, or filled with data
@@ -45,7 +45,7 @@ For example ArrayFire can be populated directly by a call to `cudaMemcpy`
 
 \snippet test/getting_started.cpp ex_getting_started_dev_ptr
 
-# ArrayFire array contents, dimentions, and properties {#getting_started_array_properties}
+# ArrayFire array contents, dimensions, and properties {#getting_started_array_properties}
 
 The [af_print](\ref af::af_print) function can be used to print arrays that
 have already been generated or an expression involving arrays:

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/arrayfire.git