summaryrefslogtreecommitdiffstats
path: root/libstdc++-v3/docs/html/faq/index.txt
diff options
context:
space:
mode:
Diffstat (limited to 'libstdc++-v3/docs/html/faq/index.txt')
-rw-r--r--libstdc++-v3/docs/html/faq/index.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt
index 4b7487b86dd..9aff7fb2d67 100644
--- a/libstdc++-v3/docs/html/faq/index.txt
+++ b/libstdc++-v3/docs/html/faq/index.txt
@@ -89,7 +89,7 @@
That means that all of the Standard classes and functions (such as
string, vector<>, iostreams, and algorithms) will be freely available
and fully compliant. Programmers will no longer need to "roll their
- own" nor be worried about platform-specific incompatabilities.
+ own" nor be worried about platform-specific incompatibilities.
_________________________________________________________________
1.3 Who's in charge of it?
@@ -314,7 +314,7 @@
Since the goal of ISO Standardization is for all C++ implementations
to be able to share code, the final libstdc++ should, in theory, be
- useable under any ISO-compliant compiler. It will still be targeted
+ usable under any ISO-compliant compiler. It will still be targeted
and optimized for GCC/g++, however.
_________________________________________________________________
OpenPOWER on IntegriCloud