From 6105b5f7d143e654f19b5f347b802266a499c496 Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Wed, 28 Feb 2018 04:01:25 +0000 Subject: [PATCH] spelling: intuitive --- src/See/dagc.h | 2 +- src/SeeDll/dagc.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/See/dagc.h b/src/See/dagc.h index 6162c4a3..e676e40c 100644 --- a/src/See/dagc.h +++ b/src/See/dagc.h @@ -207,7 +207,7 @@ int dagc_stats(dagc_t *dagcfd, dagc_stats_t *ps); * for open, close and write. However, if the programmer uses these functions, he is more protected * against file format changes (for example if the file format will have an header in the future). * Moreover, assuming that the user knows the file format is a bad practice: providing - * simple simple save functionality is more intutive and user-friendly. + * simple simple save functionality is more intuitive and user-friendly. */ int dagc_dumpfile_open(dagc_t *dagcfd, char* name); diff --git a/src/SeeDll/dagc.h b/src/SeeDll/dagc.h index 6162c4a3..e676e40c 100644 --- a/src/SeeDll/dagc.h +++ b/src/SeeDll/dagc.h @@ -207,7 +207,7 @@ int dagc_stats(dagc_t *dagcfd, dagc_stats_t *ps); * for open, close and write. However, if the programmer uses these functions, he is more protected * against file format changes (for example if the file format will have an header in the future). * Moreover, assuming that the user knows the file format is a bad practice: providing - * simple simple save functionality is more intutive and user-friendly. + * simple simple save functionality is more intuitive and user-friendly. */ int dagc_dumpfile_open(dagc_t *dagcfd, char* name);