Skip to content

Commit e9972cd

Browse files
Merge pull request #1799 from IgniteUI/mt/fix-syntax
fix-syntax
2 parents 787cdcd + f7a9bf1 commit e9972cd

21 files changed

+35
-33
lines changed

doc/en/components/charts/features/chart-data-aggregations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ namespace: Infragistics.Controls.Charts
1111

1212
In the {ProductName} `CategoryChart` control Data Aggregations feature allows you to group data in the chart by unique values on the `XAxis` and then sort those groups. You may then apply summaries which will be reflected by the range of the `YAxis` and will be displayed in the tooltip when hovering the series.
1313

14-
# {Platform} Data Aggregations Example
14+
## {Platform} Data Aggregations Example
1515

1616
The following example depicts a [Column Chart](../types/column-chart.md) that groups by the Country member of the `XAxis` and can be changed to other properties within each data item such as Product, MonthName, and Year to aggregate the sales data. Also a summary and sort option is available to get a desirable order for the grouped property.
1717

doc/en/components/charts/features/chart-data-legend.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The unit column displays an abbreviation symbol on the right side of value colum
7272

7373
### Customizing Columns
7474

75-
You can customize text displayed in the **Label** and **Unit** columns using properties that end with **MemberAsLegendLabel** and **MemberAsLegendUnit** on each series. The following table shows some possible customizations of the **Label** and **Unit** columns.
75+
You can customize text displayed in the **Label** and **Unit** columns using properties that end with **MemberAsLegendLabel** and **MemberAsLegendUnit** on each series. The following table shows some possible customizations of the **Label** and **Unit** columns.
7676

7777
| Type of Series | Series Properties |
7878
| ------|---- |
@@ -90,7 +90,7 @@ Legend items can be positioned in a vertical or table structure via the `LayoutM
9090

9191
eg.
9292

93-
<img src="../../../images/general/layout_mode.png" />
93+
<img src="../../../images/general/layout_mode.png" alt="Layout Mode" />
9494

9595
## {Platform} Data Legend Styling
9696

doc/en/components/charts/features/chart-data-selection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ The following example shows the combination of both `SelectionColorFill` and `Au
5353

5454
## Configuring Multiple Selection
5555

56-
Other selection modes offer various methods of selection. For example using `SelectionBehavior` with `PerDataItemMultiSelect` will effect all series in entire category when multiple series are present while allowing selection across categories. Compared to `PerDataItemSingleSelect`, only a single category of items can be selected at a time. This is useful if multiple series are bound to different datasources and provides greater control of selection between categories.
56+
Other selection modes offer various methods of selection. For example using `SelectionBehavior` with `PerDataItemMultiSelect` will affect all series in entire category when multiple series are present while allowing selection across categories. Compared to `PerDataItemSingleSelect`, only a single category of items can be selected at a time. This is useful if multiple series are bound to different datasources and provides greater control of selection between categories.
5757
`PerSeriesAndDataItemGlobalSingleSelect` allows single series selection across all categories at a time.
5858

5959
`sample="/charts/category-chart/selection-multiple-modes", height="450", alt="{Platform} Category Chart Selection Multiple Modes Example"`

doc/en/components/charts/features/chart-data-tooltip.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ Legend items can be positioned in a vertical or table structure via the `LayoutM
113113

114114
eg.
115115

116-
<img src="../../../images/general/layout_mode.png" />
116+
<img src="../../../images/general/layout_mode.png" alt="Layout Mode" />
117117

118118

119119
## {Platform} Data Tooltip Styling

doc/en/components/charts/types/area-chart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,5 +206,5 @@ The following table lists API members mentioned in above sections:
206206
| Polar Spline Area | `XamDataChart` | `PolarSplineAreaSeries` |
207207
| Stacked Area | `XamDataChart` | `StackedAreaSeries` |
208208
| Stacked Spline Area | `XamDataChart` | `StackedSplineAreaSeries` |
209-
| Stacked 100% Area | `XamDataChart` | `Stacked100AreaSeries`
209+
| Stacked 100% Area | `XamDataChart` | `Stacked100AreaSeries` |
210210
| Stacked 100% Spline Area | `XamDataChart` | `Stacked100SplineAreaSeries` |

doc/en/components/dashboard-tile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ You are not locked into a single visualization when you bind the `DataSource`, a
130130

131131
The visualization or properties of the visualization are also configurable using the `Toolbar` at the top of the control. This `Toolbar` has the default tools for the current visualization with the addition of four Dashboard Tile specific ones, highlighted below:
132132

133-
<img src="../images/dashboard-tile-toolbar.png" />
133+
<img src="../images/dashboard-tile-toolbar.png" alt="Dashboard Tile Toolbar"/>
134134

135135
From left to right:
136136

doc/en/components/geo-map-binding-shp-file.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,8 +57,7 @@ The `ShapefileRecord` class provides properties for storing geo-spatial data, li
5757

5858
| Property | Description |
5959
|--------------|---------------|
60-
|`Points`|Contains all the points in one geo-spatial shape loaded from a shape file (.shp). For example, the country of Japan in shape file would be represented as a list of a list of points object, where:<ul><li>The first list of points describes shape of Hokkaido island</li><li>The second list of points describes shape of Honshu island</li><li>The third list of points describes shape of Kyushu island</li><li>The fourth list of points describes shape of Shikoku island
61-
</li></ul>|
60+
|`Points`|Contains all the points in one geo-spatial shape loaded from a shape file (.shp). For example, the country of Japan in shape file would be represented as a list of a list of points object, where:<ul><li>The first list of points describes shape of Hokkaido island</li><li>The second list of points describes shape of Honshu island</li><li>The third list of points describes shape of Kyushu island</li><li>The fourth list of points describes shape of Shikoku island</li></ul>|
6261
| `Fields` |Contains a row of data from the shape database file (.dbf) keyed by a column name. For example, a data about county of Japan which includes population, area, name of a capital, etc.|
6362

6463
This data structure is suitable for use in most Geographic Series as long as appropriate data columns are mapped to them.

doc/en/components/geo-map-display-bing-imagery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The {Platform} `BingMapsMapImagery` is geographic imagery mapping service provid
1919

2020

2121
<!-- `sample="/maps/geo-map/display-bing-imagery", height="500", alt="{Platform} Displaying Imagery from Bing Maps Example"` -->
22-
<img src="../images/general/BingMapsImagery.png" />
22+
<img src="../images/general/BingMapsImagery.png"alt="Angular Bing Maps Imagery" />
2323

2424

2525
<div class="divider--half"></div>

doc/en/components/geo-map-shape-files-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Before plotting geo-spatial data in the control, one should get familiar with th
3434

3535
## Shape Files Format
3636

37-
The {Platform} `XamGeographicMap` control uses popular [Shape Files](http://en.wikipedia.org/wiki/Shapefile#Overview) format as one of the sources for geo-spatial data. Shape files are usually shipped with other file types, generally files with *.shp*, *.shx*, and *.dbf* extensions.
37+
The {Platform} `XamGeographicMap` control uses popular [Shape Files](http://en.wikipedia.org/wiki/Shapefile#Overview) format as one of the sources for geo-spatial data. Shape files are usually shipped with other file types, generally files with _.shp_, _.shx_, and _.dbf_ extensions.
3838

3939
The following table provides basic information and purpose for each type of shape files.
4040

doc/en/components/interactivity/accessibility-compliance.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,11 @@ The matrix below provides a high-level outline of the accessibility support prov
3232

3333
|**Component/Principle**|<a title="A text equivalent for every non-text element shall be provided (e.g., via 'alt', 'longdesc', or in element content)."> (a)</a><br/>|<a title="Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation">(b)</a><br/>|<a title="Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup">(c)</a><br/>|<a title="Documents shall be organized so they are readable without requiring an associated style sheet">(d)</a><br/>|<a title="Redundant text links shall be provided for each active region of a server-side image map">(e)</a><br/>|<a title="Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape">(f)</a><br/>|<a title="Row and column headers shall be identified for data tables">(g)</a><br/>|<a title="Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers">(h)</a><br/>|<a title="Frames shall be titled with text that facilitates frame identification and navigation">(i)</a><br/>|<a title="Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz">(j)</a><br/>|<a title="A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way">(k)</a><br/>|<a title="When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.">(l)</a><br/>|<a title="When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21 (a)">(m)</a><br/>|<a title="When electronic forms are designed to be completed online, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.">(n)</a><br/>|<a title="A method shall be provided that permits users to skip repetitive navigation links.">(o)</a><br/>|<a title="When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required">(p)</a><br/>|
3434
|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|
35-
|*Grids*|||||||||||||||||
35+
|_Grids_|||||||||||||||||
3636
| - Grid|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />||||<span class="greenCheck" />|<span class="greenCheck" />||<span class="greenCheck" />*||<span class="redCheck" />||<span class="greenCheck" />||<span class="redCheck" />|
3737
| - HierarchicalGrid|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />||||<span class="greenCheck" />|<span class="greenCheck" />||<span class="greenCheck" />*||<span class="redCheck" />||<span class="greenCheck" />||<span class="redCheck" />|
3838
| - TreeGrid|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />||||<span class="greenCheck" />|<span class="greenCheck" />||<span class="greenCheck" />*||<span class="redCheck" />||<span class="greenCheck" />||<span class="redCheck" />|
39-
|*Other*||||||||||<span class="greenCheck" />*|||||||
39+
|_Other_||||||||||<span class="greenCheck" />*|||||||
4040
| - Avatar|<span class="greenCheck" />||<span class="greenCheck" />|<span class="greenCheck" />||||||||<span class="greenCheck" />||<span class="greenCheck" />|||
4141
| - Badge|<span class="greenCheck" />||<span class="greenCheck" />|||||||||<span class="greenCheck" />||<span class="greenCheck" />|||
4242
| - Bottom navigation|||<span class="greenCheck" />|||||||<span class="greenCheck" />*||<span class="redCheck" />||<span class="greenCheck" />|||
@@ -78,12 +78,12 @@ The matrix below provides a high-level outline of the accessibility support prov
7878
||||
7979
|---|---|---|
8080
|<span class="greenCheck" />|The control/component is completely accessible in this particular area.||
81-
|<span class="greenCheck" />*|The control/component is accessible in this particular area after implementing certain configurations| Example: Use *NoopAnimationsModule* utility module to allow disabling of animations|
81+
|<span class="greenCheck" />*|The control/component is accessible in this particular area after implementing certain configurations| Example: Use _NoopAnimationsModule_ utility module to allow disabling of animations|
8282
|<span class="redCheck" />|The control/component is not entirely accessible unless you perform some sort of action.||
8383
|'white space'|this particular rule does not apply to the control||
8484

8585
> [!WARNING]
86-
> The table above is relevant only to the *Default theme* of Ignite UI for {Platform} theming library. The checklist compliance might be different when it comes to custom themes, typography and any visual changes related to animations and colors.
86+
> The table above is relevant only to the _Default theme_ of Ignite UI for {Platform} theming library. The checklist compliance might be different when it comes to custom themes, typography and any visual changes related to animations and colors.
8787
8888
### Compliance Information
8989

@@ -110,11 +110,11 @@ The matrix below provides a high-level outline of the accessibility support prov
110110

111111
|**Component/Guideline**|<a title="Text Alternatives - Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.">1.1</a><br/>|<a title="Time-based Media - Provide alternatives for time-based media.">1.2</a><br/>|<a title="Adaptable - Create content that can be presented in different ways (for example simpler layout) without losing information or structure">1.3 </a><br/>|<a title="Distinguishable - Make it easier for users to see and hear content including separating foreground from background.">1.4</a><br/>|<a title="Keyboard Accessible - Make all functionality available from a keyboard">2.1</a><br/>|<a title="Enough Time - Provide users enough time to read and use content.">2.2</a><br/>|<a title="Seizures and Physical Reactions - Do not design content in a way that is known to cause seizures or physical reactions.">2.3</a><br/>|<a title="Navigable - Provide ways to help users navigate, find content, and determine where they are">2.4</a><br/>|<a title="Input Modalities - Make it easier for users to operate functionality through various inputs beyond keyboard.<br/>">2.5</a><br/>|<a title="Readable - Make text content readable and understandable">3.1</a><br/>|<a title="Predictable - Make Web pages appear and operate in predictable ways">3.2</a><br/>|<a title="Input Assistance - Help users avoid and correct mistakes">3.3</a><br/>|<a title="Compatible - Maximize compatibility with current and future user agents, including assistive technologies">4.1 </a><br/>|
112112
|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|
113-
|*Grids*||||||||||||||
113+
|_Grids_||||||||||||||
114114
| - Grid|<span class="greenCheck" />||<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*|<span class="greenCheck" />|<span class="redCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*||<span class="greenCheck" />|
115115
| - HierarchicalGrid|<span class="greenCheck" />||<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*|<span class="greenCheck" />|<span class="redCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*||<span class="greenCheck" />|
116116
| - TreeGrid|<span class="greenCheck" />||<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*|<span class="greenCheck" />|<span class="redCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*||<span class="greenCheck" />|
117-
|*Other*|||||||<span class="greenCheck" />*|||||||
117+
|_Other_|||||||<span class="greenCheck" />*|||||||
118118
| - Avatar|<span class="greenCheck" />|||<span class="greenCheck" />||<span class="greenCheck" />||||<span class="greenCheck" />|<span class="greenCheck" />*|||
119119
| - Badge|<span class="greenCheck" />|||<span class="greenCheck" />||<span class="greenCheck" />||||<span class="greenCheck" />|<span class="greenCheck" />*|||
120120
| - Banner|||<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*|<span class="greenCheck" />*||<span class="greenCheck" />|<span class="greenCheck" />|<span class="greenCheck" />*|||
@@ -160,12 +160,12 @@ The matrix below provides a high-level outline of the accessibility support prov
160160
||||
161161
|---|---|---|
162162
|<span class="greenCheck" />|The control/component is completely accessible in this particular area.||
163-
|<span class="greenCheck" />*|The control/component is accessible in this particular area after implementing certain configurations|Example 1: Guideline 2.2. For certain components additional actions and time parameters should be set; Example 2: Guideline 2.3. Use *NoopAnimationsModule* utility module to allow disabling of animations;|
163+
|<span class="greenCheck" />*|The control/component is accessible in this particular area after implementing certain configurations|Example 1: Guideline 2.2. For certain components additional actions and time parameters should be set; Example 2: Guideline 2.3. Use _NoopAnimationsModule_ utility module to allow disabling of animations;|
164164
|<span class="redCheck" />|The control/component is not entirely accessible unless you perform some sort of action.||
165165
|'white space'|this particular rule does not apply to the control||
166166

167167
> [!WARNING]
168-
> The table above is relevant only to the *Default theme* of Ignite UI for {Platform} theming library. The checklist compliance might be different when it comes to custom themes, typography and any visual changes related to animations and colors.
168+
> The table above is relevant only to the _Default theme_ of Ignite UI for {Platform} theming library. The checklist compliance might be different when it comes to custom themes, typography and any visual changes related to animations and colors.
169169
170170
### Compliance Information
171171

0 commit comments

Comments
 (0)