changeset 170:bb63c0acc335 default tip

Fixed some spelling & grammar.
author Oleksandr Gavenko <gavenkoa@gmail.com>
date Wed, 14 Nov 2018 00:56:33 +0200
parents 60cfca94c50a
children
files 09363304-ddc3-11e6-aa07-485b39c42d0f/index.rst 144b3e26-1301-4cc6-8e87-9395163ea633/index.rst 4b468ff0-df21-11e6-9c0f-485b39c42d0f/index.rst
diffstat 3 files changed, 8 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/09363304-ddc3-11e6-aa07-485b39c42d0f/index.rst	Wed Nov 14 00:42:31 2018 +0200
+++ b/09363304-ddc3-11e6-aa07-485b39c42d0f/index.rst	Wed Nov 14 00:56:33 2018 +0200
@@ -82,7 +82,7 @@
           beg +=1
           break
 
-with unnecessary check ``beg < end - 1`` because we actually look for condtion ``s[beg] == ch``.
+with unnecessary check ``beg < end - 1`` because we actually look for condition ``s[beg] == ch``.
 That corresponds to my::
 
   while s[beg] != ch:
--- a/144b3e26-1301-4cc6-8e87-9395163ea633/index.rst	Wed Nov 14 00:42:31 2018 +0200
+++ b/144b3e26-1301-4cc6-8e87-9395163ea633/index.rst	Wed Nov 14 00:56:33 2018 +0200
@@ -6,16 +6,16 @@
 :updated: 2017-03-05
 :tags: sql, oracle
 
-We need to reset our FlyWay history due to major DB refactoring. All changes would be squashed into
-single that creates base schema so you can recreate database from scratch. But we don't want
+We need to reset our Flyway history due to major DB refactoring. All changes would be squashed into
+single that creates a base schema to be able to recreate database from scratch. But we don't want
 conflicts with existing tables in production.
 
-MySQL database has syntax to prevent error on ``create table`` if table is already exist::
+MySQL database has syntax to prevent error on ``create table`` if table already exists::
 
   create table if not exist "TBL" (...);
 
-Unfortunately Oracle database hasn't such syntax. But it can be mimicked with PL/SQL code block and
-exception handling. Because PL/SQL code doesn't allow DDL code we use dynamic queries::
+Unfortunately Oracle database doesn't have such syntax. It can be mimicked with PL/SQL code block
+and exception handling. Because PL/SQL code doesn't allow DDL code dynamic queries are used::
 
   declare
   begin
--- a/4b468ff0-df21-11e6-9c0f-485b39c42d0f/index.rst	Wed Nov 14 00:42:31 2018 +0200
+++ b/4b468ff0-df21-11e6-9c0f-485b39c42d0f/index.rst	Wed Nov 14 00:56:33 2018 +0200
@@ -14,7 +14,7 @@
 Fail-fast and fail-safe iterators
 =================================
 
-Most collection implementation doesn't support modification during looping across interator. It
+Most collection implementation doesn't support modification during looping across iterator. It
 doesn't matter if modification come from same thread or another.
 
 In some cases implementation can detect such situation and throw
@@ -25,7 +25,7 @@
 .. note::
 
   Note that fail-fast behavior cannot be guaranteed as it is, generally speaking, impossible to make
-  any hard guarantees in the presence of unsynchronized concurrent modification. Fail-fast
+  any hard guarantees in the presence of asynchronous concurrent modification. Fail-fast
   operations throw ConcurrentModificationException on a best-effort basis. Therefore, it would be
   wrong to write a program that depended on this exception for its correctness:
   **ConcurrentModificationException should be used only to detect bugs**.