differences-17-18.rst

@@ -14,25 +14,25 @@ Differences from 1.7
 
 Carousel
 --------
-- Carousel has no backward compatibility, since it was experimental in 1.7. The new Carousel does not support data stores. There are two subclasses that supports data stores. Use `DataCarousel <DataCarousel>`_ if you want to use carousel with dojo.data. Use `StoreCarousel <StoreCarousel>`_ if you want to use carousel with dojo.store.
+- Carousel has no backward compatibility, since it was experimental in 1.7. The new Carousel does not support data stores. There are two subclasses that support data stores. Use `DataCarousel <DataCarousel>`_ if you want to use carousel with dojo.data. Use `StoreCarousel <StoreCarousel>`_ if you want to use carousel with dojo.store.
 
 FixedSplitter
 -------------
-- FixedSplitter.css is no longer in the themes/common folder. It is in a device theme folder. (e.g. themes/iphone/FixedSplitter.css)
+- FixedSplitter.css is no longer in the themes/common folder. It is in the device theme folder. (e.g. themes/iphone/FixedSplitter.css)
 
 FlippableView
 -------------
 - FlippableView was deprecated in 1.7, and removed in 1.8. Use SwapView instead.
 
 ListItem
 --------
-- The sync property is no longer supported. It always behaves in the async manner.
+- The sync property is no longer supported. It always behaves asynchronously.
 - The btnClass property is no longer supported. Use rightIcon instead.
 - The btnClass2 property is no longer supported. Use rightIcon2 instead.
 
 SpinWheel
 ---------
-- SpinWheel.css is no longer in the themes/common folder. It is in a device theme folder. (e.g. themes/iphone/SpinWheel.css)
+- SpinWheel.css is no longer in the themes/common folder. It is in the device theme folder. (e.g. themes/iphone/SpinWheel.css)
 - getValue() is no longer supported. Use get("values") instead.
 - setValue() is no longer supported. Use set("values", newValue) instead.
 
@@ -48,9 +48,9 @@ Switch
 
 TabBar
 ------
-In 1.7 or older, barType="segmentedControl" produced different UI
+In 1.7 or older, barType="segmentedControl" produced different UIs
 according to the current theme. In the iphone theme, it was a
-segmented control. But in other themes, it was tabs with or without
+segmented control, but in other themes, it was tabs with or without
 icons. In 1.8, however, barType="segmentedControl" always produces a
 segmented control UI regardless of the current theme.
 
@@ -62,8 +62,8 @@ If you still need the old behavior,
 
 should produce a segmented control for the iphone theme, and a tall
 tab bar for the other themes. You need to use deviceTheme.js to
-specify barType that way.  Also, if you want to hide tab icons on the
-segmented control in the iphone theme, you could apply css like this:
+specify barType that way.  Also, if you want to hide the tab icons of the
+segmented control in the iphone theme, you could apply a css like this:
 
 ```html
   <style>
@@ -73,7 +73,7 @@ segmented control in the iphone theme, you could apply css like this:
   </style>
 ```
 
-See test_ScrollableView-demo.html for usage example.
+See test_ScrollableView-demo.html for an example usage.
 
 TabBarButton
 -------------
@@ -113,14 +113,14 @@ New Features in 1.8
 ProgressIndicator
 -----------------
 
-ProgressIndicator was a singleton non-widget module. In 1.8, it became an ordinary widget which inherits from _WidgetBase. A new enhanced ProgressIndicator has ability to customize size, color, and display position. See `ProgressIndicator <ProgressIndicator>`_ for details.
+ProgressIndicator was a singleton non-widget module. In 1.8, it is an ordinary widget which inherits from _WidgetBase. A new enhanced ProgressIndicator has the ability to customize size, color, and display position. See `ProgressIndicator <ProgressIndicator>`_ for details.
 
 dojox.mobile.parser
 -------------------
 
 - stopParser
 
-To support dojox.mvc, the stopParser feature was added to dojox.mobile.parser. If a widget has the stopParser flag, the parser stops parsing its child widgets. dojo.parser has this capability, but dojox.mobile.parser didn't have it until 1.8 to keep the code size minimum.
+To support dojox.mvc, the stopParser feature was added to dojox.mobile.parser. If a widget has the stopParser flag, the parser stops parsing its child widgets. dojo.parser has this capability, but dojox.mobile.parser didn't until 1.8 to keep the code size small.
 
 - New data-dojo-type syntax