Improving Your Code Productivity

Cleaning Up Your Code

The Tizen Studio provides various features for the productive development. This topic describes the Code Beautifier and Code Minifier features that you can use with the Tizen Web Editor.

The Tizen Studio provides features to assist with productive development. This topic describes the Code Beautifier and Code Minifier features in the Tizen Web Editor.

Using the Code Beautifier

The Code Beautifier is a tool that can help you understand code and make it easier to read. For example, to match the indentation and alignment in the same style automatically, you can improve your coding performance.

The Code Beautifier is a tool that can help you understand code by making it easier to read. For example, by inserting indentations and alignments automatically, you can code more efficiently without compromising readability.

The Code Beautifier has the following features for beautifying HTML, CSS, and JavaScript:

Beautifying code to a minified form
Beautifying code from a minified form
Inserting indentation
Inserting carriage returns

You can use the Code Beautifier in 3 ways:

In the Project Explorer view, right-click a CSS or JavaScript file in the project and select Code Beautifier. -
A beautified file with the .beaut.<extension> extension is generated, and a notification dialog is displayed in the lower-right section of the Tizen Studio.
+
In the Project Explorer view, right-click an HTML, CSS, or JavaScript file in the project and select Code Beautifier. +
A beautified file with the .beaut.<extension> extension is generated, and a notification popup appears in the Tizen Studio.
In the Source Editor view, right-click the code and select Code Beautifier.
In the Source Editor or Project Explorer view, use the Ctrl + 6 hotkey.

In case you use the Code Beautifier in the Source Editor view, no new file is generated. The original file is changed instead.

If you use the Code Beautifier in the Source Editor view, no new file is generated. The original file is changed instead.

Figure: Code Beautifier with CSS file - before beautifying

Code Beautifier with CSS file - before beautifying

@@ -69,8 +69,8 @@

Using the Code Minifier

Minification is the process of compressing the code from the original size to the smallest size. It does not affect the operation of the code. The Code Minifier is a smart compression tool, which removes or modifies some unnecessary characters from the code.

The Code Minifier removes characters, such as white spaces, new line, commented out code, and finally all the code is on 1 line.

Minification is the process of compressing the code from its original size to the smallest size, without affecting its operation. The Code Minifier is a smart compression tool which removes or modifies unnecessary characters from the code.

The Code Minifier removes characters, such as white space, line breaks, and commented-out code. It then places all the code on 1 line.

The Code Minifier has the following features:

Minifying HTML @@ -84,7 +84,7 @@

Minifying CSS

Removing comments and white space
Removing the last semicolon
Removing the final semicolon
Removing extra semicolons
Removing empty declarations
Removing, for example, zero values, floats, and color values

You can use the Code Minifier in 3 ways:

In the Project Explorer view, right-click a CSS or JavaScript file in the project and select Code Minifier. -
A minified (compressed) file with the .min.<extension> extension is generated, and a notification dialog is displayed in the lower-right section of the Tizen Studio.
+
In the Project Explorer view, right-click an HTML, CSS, or JavaScript file in the project and select Code Minifier. +
A minified (compressed) file with the .min.<extension> extension is generated, and a notification popup appears in the Tizen Studio.
In the Source Editor view, right-click the code and select Code Minifier.
In the Source Editor or Project Explorer view, use the Ctrl + 5 hotkey.

In case you use the Code Minifier in the Source Editor view, no new file is generated. The original file is changed instead.

If you use the Code Minifier in the Source Editor view, no new file is generated. The original file is changed instead.

Figure: Code Minifier with CSS file - before minifying

Code Minifier with CSS file - before minifying

Configuring Applications

The Tizen Web application configuration file is composed of XML elements, including the <widget> element as its root and other elements. These elements represent the application information, such as configuration elements and Tizen extending configuration elements for mobile and wearable applications.

The Tizen Web application configuration file is composed of XML elements, including the <widget> element as its root and other elements. These elements represent application information, such as configuration elements and Tizen extending configuration elements for mobile and wearable applications.

This configuration information is used when you install or run the Tizen Web application on the Tizen platform. The Tizen Web application project must have the config.xml file in the project root directory.

The configuration file can be easily edited with the Web application configuration editor (form editor), or you can modify the XML structure directly using the configuration source editor. With the form editor, you can set the project configuration (manifest), even if you have no experience of developing a Tizen Web application project. If you are fluent with the configuration file XML structure, you can create the configuration file directly through the configuration source editor.

The configuration file can be easily edited with the Web application configuration editor (form editor), or you can modify the XML structure directly using the configuration source editor. With the form editor, you can set the project configuration (manifest), even if you have no experience with developing a Tizen Web application project. If you are fluent with the configuration file XML structure, you can create the configuration file directly through the configuration source editor.

Note @@ -317,7 +317,7 @@

Configuration Elements

The following tables summarize of the W3C configuration elements used in the config.xml file of the Web application. For more information on the W3C element details, see Widget Packaging and XML Configuration (the details of the Tizen extending configuration elements are described in Extending Configuration Elements in Mobile Applications and Extending Configuration Elements in Wearable Applications). For a quick view of the element hierarchy, see Configuration Element Hierarchy.

The following tables summarize the W3C configuration elements used in the config.xml file of a Web application. For more information on the W3C element details, see Widget Packaging and XML Configuration (the details of the Tizen extending configuration elements are described in Extending Configuration Elements in Mobile Applications and Extending Configuration Elements in Wearable Applications). For a quick view of the element hierarchy, see Configuration Element Hierarchy.

@@ -360,7 +360,7 @@ - - - -

<author> element
Represents the person that created the Web application. Expected children: +	Represents the person who created the Web application. Expected children: `<span>` and `<text node>` Attributes: `xml:lang` `dir` @@ -437,7 +437,7 @@	<name> element
Represents the Web application name used for example, in the application menu. Expected children: +	Represents the Web application name used, for example, in the application menu. Expected children: `<span>` and `<text node>` Attributes: `xml:lang` `dir` @@ -495,11 +495,11 @@ Extending Configuration Elements in Mobile Applications - The following sections show additional configuration elements used in the `config.xml` file of the Web application, but not included in the Widget Packaging and XML Configuration guidelines. For a quick view of the entire element hierarchy, see Configuration Element Hierarchy. + The following sections show additional configuration elements used in the `config.xml` file of a Web application, but not included in the Widget Packaging and XML Configuration guidelines. For a quick view of the entire element hierarchy, see Configuration Element Hierarchy. Note - The extension elements are denoted as though the `xmlns:tizen="http://tizen.org/ns/widgets"` namespace declaration was in effect. + The extension elements are denoted as though the `xmlns:tizen="http://tizen.org/ns/widgets"` namespace declaration is in effect. The maximum length of the attribute and the element (except `<tizen:metadata>`, W3C preference element) can be limited to 2048 bytes. In this case, leftover bytes are ignored. @@ -620,7 +620,7 @@ Attributes: `id` Mandatory; Tizen application ID, which is a combination of the Tizen package ID and project name. The application ID is unique among applications on the device. The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and the maximum value is 52 bytes. - `package` Mandatory; Tizen package ID generated by the Tizen Studio, comprises of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Tizen Store. + `package` Mandatory; Tizen package ID generated by the Tizen Studio, consisting of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Tizen Store. `required_version` Mandatory; Tizen API version required for running the Web application `launch_mode` Optional; sets which launch mode is supported (available values: `single` (default), `group`, `caller`) `single`: launched as a main application @@ -726,7 +726,7 @@	<tizen:content-security-policy-report-only/> element
Used to define an additional content security policy for a packaged or hosted application for monitoring purposes. +	Used to define an additional content security policy, for monitoring purposes, for a packaged or hosted application. Occurrences: 0 or more @@ -753,7 +753,7 @@ Note - Even though the `<feature/>` element is defined in the Widget Packaging and XML Configuration guidelines, in Tizen, an extended version is used. + Even though the `<feature/>` element is defined in the Widget Packaging and XML Configuration guidelines, an extended version is used in Tizen. Occurrences: @@ -810,7 +810,7 @@	<tizen:privilege/> element
Used to get the required API access privileges for the Web application. +	Used to get the required API access privileges for a Web application. Occurrences: 0 or more (if duplicates, the first occurrence is considered and all others ignored) @@ -909,11 +909,11 @@

Extending Configuration Elements in Wearable Applications

The following sections show additional configuration elements used in the config.xml file of the Web application, but not included in the Widget Packaging and XML Configuration guidelines. For a quick view of the entire element hierarchy, see Configuration Element Hierarchy.

The following sections show additional configuration elements used in the config.xml file of a Web application, but not included in the Widget Packaging and XML Configuration guidelines. For a quick view of the entire element hierarchy, see Configuration Element Hierarchy.

Note - The extension elements are denoted as though the xmlns:tizen="http://tizen.org/ns/widgets" namespace declaration was in effect. + The extension elements are denoted as though the xmlns:tizen="http://tizen.org/ns/widgets" namespace declaration is in effect.

The maximum length of the attribute and the element (except tizen:metadata, W3C preference element) can be limited to 2048 bytes. In that case, leftover bytes are ignored.

@@ -1021,7 +1021,7 @@ <tizen:app-widget/> element - Used to define the basic information about a Web widget. + Used to define the basic information for a Web widget.

Occurrences:

0 or more

Attributes:

id
Mandatory; unique ID of the Web widget in the <TIZEN_APPLICATION_ID>.<STRING> format, where <STRING> comprises 1 or more characters (0~9, a~z, A~Z)
id
Mandatory; unique ID of the Web widget in the <TIZEN_APPLICATION_ID>.<STRING> format, where <STRING> consists of 1 or more characters (0~9, a~z, A~Z)
primary
Mandatory; defines a primary Web widget among the Web widgets in a Web application (available values: true, false)
max-instance
Optional; limits the number of widget instances concurrently executable for a Web application. When omitted or its value is 0, unlimited number of widget instances are supported. The expected value is integer.

@@ -1058,7 +1058,7 @@ <tizen:widget-label/> element - Used to define the name of Web widget. + Used to define the name of the Web widget.

Occurrences:

1 or more

Attributes:

id
Mandatory; Tizen application ID, which is a combination of the Tizen wearable package ID and project name. The application ID is unique among applications on the device.
The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and the maximum value is 52 bytes.
package
Mandatory; Tizen wearable package ID generated by the Tizen Studio, comprises of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Samsung Apps.
package
Mandatory; Tizen wearable package ID generated by the Tizen Studio, consisting of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Samsung Apps.
required_version
Mandatory; Tizen API version required for running the Web application

ambient_support

Optional; sets whether the Web application supports the ambient mode (available values: enable, disable (default))

If this option is enabled, the application can be shown in the ambient mode.

Since: 2.3.1 @@ -1239,7 +1239,7 @@ <tizen:content/> element - Used to define the start page to be hosted on an external server. + Used to define a start page hosted on an external server.

Occurrences:

0 or more
If more than 1, the first occurrence is considered and all others ignored.

Occurrences:

0 or more @@ -1312,7 +1312,7 @@
Note - Even though the <feature/> element is defined in the Widget Packaging and XML Configuration guidelines, in Tizen, an extended version is used. + Even though the <feature/> element is defined in the Widget Packaging and XML Configuration guidelines, an extended version is used in Tizen.

Occurrences:
@@ -1337,7 +1337,7 @@ <tizen:ime/> element - Used to define the properties of IME (Input Method Editor) type application, which is used when you want to create your own keyboard module for Tizen platform. + Used to define the properties of an IME (Input Method Editor) type application, which is used when you want to create your own keyboard module for the Tizen platform.
Note @@ -1349,7 +1349,7 @@

Expected children:

uuid
Mandatory; universally unique, an unique identifier that distinguishes an IME from each other, displayed in the form of standard UUID (8-4-4-4-12 for a total of 36 characters)
uuid
Mandatory; universally unique, a unique identifier that distinguishes an IME from each other, displayed in the form of a standard UUID (8-4-4-4-12 for a total of 36 characters)
languages
Mandatory; list of input languages that the current IME supports

@@ -1496,8 +1496,8 @@
context-menu
Optional; sets whether the context menu is shown (available values: enable (default), disable)
If this option is enabled, the context menu is visible to the user.
encryption
Optional; sets whether Web Application resources are encrypted (available values: enable, disable (default))
If this option is enabled, the application resources(HTML, JS and CSS files) are encrypted.
screen-orientation
Optional; sets whether it locks the orientation of the Web Application (available values: portrait (default), landscape, auto-rotation)
+
encryption
Optional; sets whether Web application resources are encrypted (available values: enable, disable (default))
If this option is enabled, the application resources (HTML, JS and CSS files) are encrypted.
screen-orientation
Optional; sets whether it locks the orientation of the Web application (available values: portrait (default), landscape, auto-rotation)
- portrait or landscape: orientation is locked to portrait or landscape respectively
- auto-rotation: follows the device orientation setting

Occurrences:

Attributes:

id
Mandatory; Tizen service ID, which is a combination of the Tizen wearable package ID and service name.
The service ID is a set of characters (0~9, a~z, A~Z) and unique among service applications on the device. The minimum value is 1 byte and the maximum value is 52 bytes.
on-boot
Optional; sets whether the service application is launched automatically on device boot (available values: true, false (default))
on-boot
Optional; sets whether the service application is launched automatically on device boot (available values: true, false (default))
Note This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices. @@ -1584,14 +1584,14 @@ <tizen:content/> element - Used to define the start page of the Web Service Application. + Used to define the start page of the Web service application.
Occurrences:
- 1
Attributes:
- src
  Mandatory; start JavaScript file path of the Web Service Application. The path is relative to the source Web application directory.
- src
  Mandatory; start JavaScript file path of the Web service application. The path is relative to the source Web application directory.
@@ -1603,7 +1603,7 @@ <tizen:name/> element - Used to define the name of Web Service Application. + Used to define the name of the Web service application.
Occurrences:
- 1 or more
-
Writing and Editing Codes
+
Writing and Editing Code

The Tizen Studio provides the following set of tools to help you write and edit code in your Web application projects:
@@ -44,8 +44,8 @@
Content Assist (Speeding Up Typing with Content Assist)
The Content Assist tool is a function provided in parts of the Tizen Studio to help you write code faster and more efficiently. It allows you to quickly type names in the context of the code.
Code Productivity (Improving Your Code Productivity) -
The Code Productivity tool provides various features for productive development. It includes the Code Beautifier and Code Minifier features that you can use with the Tizen Web Editor. The Code Beautifier can help you understand code and make it easier to read, while the Code Minifier removes or modifies some unnecessary characters from the code.
Code Cleaning (Cleaning Up Your Code) +
The Code Cleaning tools include the Code Beautifier and Code Minifier features, which you can use with the Tizen Web Editor. The Code Beautifier can help you understand code and make it easier to read, while the Code Minifier removes or modifies some unnecessary characters from the code.
REST Viewer (Using the REST Viewer)
The REST Viewer tool allows you to view and edit WADL documents, and use RESTful Web services. The REST Viewer provides facilities to emulate interaction with a Web service by composing and running requests as if it was the application that actually calls the service.
Managing Projects
You can create new application projects with the Project Wizard, and manage the existing applications in the Project Explorer view in the Tizen Studio. You can also register certificates for your applications to allow them to be published in the application stores.
Writing and Editing Codes +
Writing and Editing Code
You can edit HTML, JS, and CSS files in specific editors, and preview how the changing code affects the application screen. You can also use the live editing feature to modify the application while it is running.
-
You can use the content assist, privilege checker, and code productivity tools to speed up the code writing and verification task. With the REST Viewer tool, you can emulate interaction with a Web service. In addition, you can modify various Tizen Studio preferences to ensure that the code editing environment suits your needs.

You can use the content assist, privilege checker, and code cleaning tools to speed up the code writing and verification tasks. With the REST Viewer tool, you can emulate interaction with a Web service. In addition, you can modify various Tizen Studio preferences to ensure that the code editing environment suits your needs.

Configuring Your Application
You can manage various application functionalities and features through the application configuration file, which you can easily configure with a test or form editor. In addition, you can localize your application to use various languages and locale-specific resources by using the Web Localization view in the Tizen Studio.

Static Analyzer (Coding Rule Checker)
Contains checkers for a set of predefined coding rules. It supports 27 rules, including coding rules and Web API usage rules.
-
The Coding Rule Checker is a static analysis tool that evaluates an application by examining the JavaScript code without its execution. This type of checkers examine all possible execution paths and variable values, and then provide its their analysis result.
+
The Coding Rule Checker is a static analysis tool that evaluates an application by examining the JavaScript code without its execution. This checker examines all possible execution paths and variable values.
Dynamic Analyzer (Stale Object Checker)
Contains a checker for stale objects that cause possible memory leaks.
-
The Stale Object Checker is a dynamic analysis tool that requires executing the application on a runtime environment for its analysis. This checker examines all the JavaScript objects created during its execution and points out relatively critical staled objects.
+
The Stale Object Checker is a dynamic analysis tool that requires executing the application in a runtime environment. This checker examines all the JavaScript objects created during its execution and points out relatively critical staled objects.

Figure: JSA in the menu

JSA in the menu

The JSA analyzes JavaScript codes in the selected Web application project after selecting JavaScript files and code segments to analyze. This can be done by parsing the start HTML file (such as index.html) specified in the config.xml file.

The JSA analyzes JavaScript code in the selected Web application project after selecting JavaScript files and code segments to analyze. This can be done by parsing the start HTML file (such as index.html) specified in the config.xml file.

Figure: Checking in progress

Checking in progress

If JavaScript Analyzer detects codes that can cause potential problems during its analysis step, the problems are listed up in the Problems view. If you want to locate a possibly problematic code line, double-click the alarm in the view.

If JavaScript Analyzer detects code that can cause potential problems during its analysis step, the problems are listed in the Problems view. If you want to locate a possibly problematic code line, double-click the alarm in the view.

Figure: Problems view

Problems view

You can enable or disable the JavaScript rules in JavaScript Analyzer preferences.

To enable or disable the rules:

In the Tizen Studio, go to Window > Preferences > JavaScript Analyzer.
In the Tizen Studio, go to Window > Preferences > Tizen Studio > Web > JavaScript Analyzer.
Select or clear a rule checkbox to enable or disable the rule.

Rule 1. Use `var` to declare variables

If variables are declared without the var keyword, they are assigned to the global scope in the JavaScript language. This can be dangerous.

If variables are declared in the JavaScript language without the var keyword, they are assigned to the global scope. This can be dangerous.

For example, if the functions that have a same name are defined as following example codes, the foo function is changed whenever the func1 or func2 function is called. The foo function can not be guaranteed.

For example, if 2 functions that have the same name are defined as in the following example code, the foo function is changed whenever the func1 or func2 function is called. The foo function cannot be guaranteed.

This rule is supported by the JSLint and the Google Closure Linter. They say that "When you fail to specify var, the variable gets placed in the global context, potentially clobbering existing values. Also, if there is no declaration, it is hard to tell in what scope a variable lives."

Rule 2. Do Not Declare an Arguments Array within Functions

If the arguments array is declared with var in functions, this causes duplication with the reserved keyword arguments of JavaScript language in the functions.

If the arguments array is declared with var in functions, it causes duplication with the arguments JavaScript reserved keyword in the functions.

In the following example, the statement var arguments = []; in the function overwrites the reserved keyword arguments. As a result, the reserved keyword arguments in functions lose the feature to access the arguments of the function.

In the following example, the var arguments = []; statement in the function overwrites the arguments reserved keyword. As a result, the arguments reserved keyword in functions loses the ability to access the arguments of the function.

 function func() {
@@ -145,11 +145,11 @@ function func() {
 
 Rule 3. Do Not Capture Variables in Functions
 
-If there are captured variables in functions, they can make a closure. The closure may cause potential defects.
+If there are captured variables in functions, they can make a closure. The closure can cause potential defects.
 
 In the following example, you always expect 1 to be returned from calling the test function. However, the returned value is not always 1 because the variable x in the function outer is captured.
 
-This rule is introduced in the Google JavaScript Style Guide. They say that "The ability to create closures is perhaps the most useful and often overlooked feature of JS.One thing to keep in mind, however, is that a closure keeps a pointer to its enclosing scope. As a result, attaching a closure to a DOM element can create a circular reference and thus, a memory leak.".
+This rule is introduced in the Google JavaScript Style Guide. They say that "The ability to create closures is perhaps the most useful and often overlooked feature of JS. One thing to keep in mind, however, is that a closure keeps a pointer to its enclosing scope. As a result, attaching a closure to a DOM element can create a circular reference and thus, a memory leak."
 
  var outer = function() {
@@ -190,9 +190,9 @@ test();
 
 Rule 4. Do Not Use Extra Semicolons
 
-Extra semicolons make readability worse. In addition, it may cause wrong operation of the program. 
+Extra semicolons make readability worse. In addition, they can cause unexpected operation of the program. 
 
-This rule is described in the Google JavaScript Coding Style Guide. They say that "Extra comma and semicolon can make error.".
+This rule is described in the Google JavaScript Coding Style Guide. They say that "Extra comma and semicolon can make error."
 
  function func() {
@@ -216,7 +216,7 @@ var result = func();
 
 Rule 5. Do Not Use the Delete Keyword
 
-Deleting the property of the object needs time to operate removing the property. In addition, it changes the shape of object. The change of the object's shape may cause decrease of performance. 
+Deleting the property of an object takes time. In addition, it changes the shape of the object. The change in the object's shape can cause decreased performance. 
 
 In the following example, the property value of the instance obj is deleted using the keyword delete. This leads the instance obj not to share the shape of the constructor Obj with other instances. For that reason, the performance can be slower.
 
@@ -242,7 +242,7 @@ delete obj.value;
 
 Using multi-line string literals can cause unexpected operation of the program because of the whitespace at the beginning of each line and after the backslash (\). 
 
-This rule is introduced by the Google JavaScript Style Guide. They say that "The whitespace at the beginning of each line can't be safely stripped at compile time; whitespace after the slash will result in tricky errors; and while most script engines support this, it is not part of ECMAScript".
+This rule is introduced by the Google JavaScript Style Guide. They say that "The whitespace at the beginning of each line can't be safely stripped at compile time; whitespace after the slash will result in tricky errors; and while most script engines support this, it is not part of ECMAScript."
 
  /* Multi-line string literals can create a problem */
@@ -260,14 +260,14 @@ var str = 'The Test String \
 
 Use array and object literals instead of their constructors to avoid confusing and unexpected results.
 
-In the following example, the array arr2 that has 3 values (1, 2, and 3) can be created using an array constructor. In the same way, if the array arr1 that has a single value (1) is created using an array constructor, it is the array with the length 1, not arr[0] is 1.
+In the following example, the array arr2 that has 3 values (1, 2, and 3) can be created using an array constructor. In the same way, if the array arr1 that has a single value (1) is created using an array constructor, it is an array with length 1; it is not arr1[0] = 1.
 
-This rule is introduced by the Google Javascript Style Guide. They say that "Array constructors are error-prone due to their arguments".
+This rule is introduced by the Google Javascript Style Guide. They say that "Array constructors are error-prone due to their arguments."
 
  var x = 1
 
-/* If the variable x is 1, array arr1 is the array whose length is 1, not arr[0] is 1 */
+/* If the variable x is 1, array arr1 is an array whose length is 1; it is not arr1[0] = 1 */
 var arr1 = new Array(x);
 
 /* The array arr2 is the array which has 3 values, 1, 2, and 3 */
@@ -282,9 +282,9 @@ var arr2 = new Array(1, 2, 3);
 
 Rule 8. Do Not Modify the Prototypes of Built-in Objects
 
-Modifying built-ins, such as Object.prototype and Array.prototype, can lead to debugging issues in production and must be avoided. 
+Modifying built-ins, such as Object.prototype and Array.prototype, can lead to debugging issues in production and must be avoided.
 
-For example, the functions in prototypes of built-in objects are shared by every instance of the built-in objects. If the function is modified, it affects every instances of the built-in objects.
+For example, the functions in prototypes of built-in objects are shared by every instance of the built-in objects. If the function is modified, it affects every instance of the built-in objects.
 
 This rule is introduced by the Google Javascript Style Guide. They say that "Modifying builtins like Object.prototype and Array.prototype are strictly forbidden. It leads to hard to debug issues in production and should be avoided."
 
@@ -307,7 +307,7 @@ Object.prototype.create = function() {
 
 If a boolean variable is created by the constructor Boolean, its value is a wrapper object, not true or false. In the following example, the program always prints true because the variable bool is an object that has a value, false.
 
-This rule is introduced by the Google Javascript Style Guide. They say that "There's no reason to use wrapper objects for primitive types, plus they are dangerous". 
+This rule is introduced by the Google Javascript Style Guide. They say that "There's no reason to use wrapper objects for primitive types, plus they are dangerous."
 
  /* The variable bool is not false. It is an object with the value false */
@@ -329,7 +329,7 @@ if (bool) {
 
 Rule 10. Do Not Use the for-in Structure with Arrays
 
-If the array is used in for-in statement, the operation can be different from the normal for statement. 
+If an array is used in a for-in statement, it can operate differently than in a normal for statement.
 
 In the following example, you expect to print a, b, and c, but the program prints 0, 1, and 2.
 
@@ -352,8 +352,8 @@ for (var key in arr) {
 
 Rule 11. Do Not Use Unclosed Braces
 
-A function, an object, a code block, or a similar element which has an opening brace but no closing brace is not correct. The analysis detects this and stops with an error message.
-In the following example, the temp() function needs a closing brace to indicate that the function definition is finished. The JSA detects this and creates an alarm, and the analysis is stopped because of the error.
+A function, object, code block, or similar element which has an opening brace but no closing brace is not correct. The analysis detects this and stops with an error message.
+In the following example, the temp() function needs a closing brace to indicate that the function definition is finished. The JSA detects this and raises an alarm, and the analysis is stopped because of the error.
 
  /* The temp function needs the closing brace */
@@ -368,9 +368,9 @@ function temp() {
 
 Rule 12. Do Not Use Unclosed Comments
 
-Writing comment with only the begin comment and no closing comment is not correct. In some scenarios, it affects the implementation of the function or code block. The analysis detects this and stops with an error message.
+Writing a comment with only the begin comment and no closing comment is not correct. In some scenarios, it affects the implementation of the function or code block. The analysis detects this and stops with an error message.
 
-In the following example, the comment has no closing comment, and the for loop cannot be completed. The JSA detects it and creates an alarm, and the analysis is stopped because of the error.
+In the following example, the comment has no closing comment, and the for loop cannot be completed. The JSA detects it and raises an alarm, and the analysis is stopped because of the error.
 
  /* The comment has no close comment */
@@ -389,9 +389,9 @@ for (var i = 0; i < b; i++) {
 
 Rule 13. Do Not Use Unclosed Strings
 
-String needs to be put in the quotes, and missing a single quote is not allowed. The analysis is stopped with an error message because of this error.
+A string needs to be put in quotes, and missing a single quote is not allowed. The analysis is stopped with an error message because of this error.
 
-In the following example, the string misses a single quote, and the variable definition cannot be completed. The  JSA detects it and creates an alarm, and the analysis is stopped because of the error.
+In the following example, the string is missing a single quote, and the variable definition cannot be completed. The JSA detects it and raises an alarm, and the analysis is stopped because of the error.
 
  /* Setting value for MAX is not correct, missing single quote */
@@ -408,9 +408,9 @@ for (var i = 0; i < 10; i++) {
 
 Rule 14. Do Not Omit Semicolons
 
-Semicolon is needed in JavaScript to indicate that the declaration is finished. Missing a semicolon is not recommended, and although the analysis detects this, it proceeds without stopping.
+A semicolon is needed in JavaScript to indicate that the declaration is finished. Missing a semicolon is not recommended, and although the analysis detects this, it proceeds without stopping.
 
-In the following example, the variable a declared in the tempx() function without a semicolon, and the JSA detects it and creates an alarm.
+In the following example, the variable a is declared in the tempx() function without a semicolon. The JSA detects it and raises an alarm.
 
  /* The declaration of a needed semicolon in the end */
@@ -426,12 +426,12 @@ function tempx() {
 
 Rule 15. Do Not Begin With Operators
 
-Beginning a line with the operator is not recommended, and although the analysis detects this, it proceeds without stopping.
+Beginning a line with an operator is not recommended, and although the analysis detects this, it proceeds without stopping.
 
-In the following example, setting the value for the abc with the = operator in the new line is not correct. The operator must be in the same line as abc. The JSA detects it and creates an alarm.
+In the following example, setting the value for abc with the = operator in the new line is not correct. The operator must be in the same line as abc. The JSA detects it and raises an alarm.
 
 -/* Setting value for abc is not correct, do no begin with operator = */
+/* Setting value for abc is not correct; do not begin with operator = */
 var variable_sum = 1;
 var b = 2;
 var abc
@@ -447,7 +447,7 @@ var abc
 
 Invoking a code block with double-quotes instead of single-quotes for a string is noticed, although the analysis proceeds without stopping.
 
-In the following example, "aa" must be 'aa'. The JSA detects it and creates an alarm.
+In the following example, "aa" must be 'aa'. The JSA detects it and raises an alarm.
 
  if (true) {
@@ -464,7 +464,7 @@ if (true) {
 
 Invoking a code block with an extra comma at the end of object/array literals is noticed, although the analysis proceeds without stopping.
 
-In the following example, the last ',' must be removed. The JSA detects it and creates an alarm.
+In the following example, the last ',' must be removed. The JSA detects it and raises an alarm.
 
  var abc = [1, 2, 3,];
@@ -479,7 +479,7 @@ var abc = [1, 2, 3,];
 
 Invoking a code block with an opening brace '{' which does not appear in the same line with the statement is noticed, although the analysis proceeds without stopping.
 
-In the following example, the opening brace '{' must appear in the same line with the statement. If not, the JSA detects it and creates an alarm. 
+In the following example, the opening brace '{' must appear in the same line with the statement. If not, the JSA detects it and raises an alarm. 
 
  /* Do Not Use Wrong Opening Brace */
@@ -497,13 +497,13 @@ if (true)
 
 Web API Usage Rules
 
-Tizen Web APIs extend JavaScript APIs to enable you using the device capabilities provided by Tizen devices. The Tizen Web APIs are designed to be simple and intuitive. The following rules notify you, when the APIs are used improperly.
+Tizen Web APIs extend JavaScript APIs to enable you to use the device capabilities provided by Tizen devices. The Tizen Web APIs are designed to be simple and intuitive. The following rules notify you when the APIs are used improperly.
 
 Rule 1. Accessing Undefined API
 
-Accessing  API which not provided by the Tizen API modules are notified as an WebAPIError and the analysis proceeded.
+Accessing an API not provided by the Tizen API modules is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the tizen.alarm.gett() function does not exist in the Tizen API, so the JSA detects it and creates an alarm.
+In the following example, the tizen.alarm.gett() function does not exist in the Tizen API, so the JSA detects it and raises an alarm.
 
  /* Mistyping get as gett */
@@ -519,9 +519,9 @@ var alarm = tizen.alarm.gett(abs_alarm.id);
 
 Rule 2. Wrong Argument Number
 
-Invoking a function with a wrong argument number is notified as an WebAPIError and the analysis proceeded.
+Invoking a function with the wrong number of arguments is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the tizen.filesystem.resolve() function needs  more than 1 argument. Since the number of arguments is 1, the JSA detects it and creates an alarm.
+In the following example, the tizen.filesystem.resolve() function needs more than 1 argument. Since the number of arguments is 1, the JSA detects it and raises an alarm.
 
  /* The number of arguments is wrong (2 or more arguments required) */
@@ -537,9 +537,9 @@ tizen.filesystem.resolve('images'
 
 Rule 3. Missing Error Handling
 
-Invoking an asynchronous function without an error callback is notified as an WebAPIError and the analysis proceeded.
+Invoking an asynchronous function without an error callback is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the tizen.filesystem.resolve() function needs an error callback as its third argument. Because the error callback does not exist, the JSA detects it and creates an alarm.
+In the following example, the tizen.filesystem.resolve() function needs an error callback as its third argument. Because the error callback does not exist, the JSA detects it and raises an alarm.
 
  tizen.filesystem.resolve('images', function(dir) {
@@ -557,9 +557,9 @@ tizen.filesystem.resolve('images', function(dir) {
 
 Rule 4. Missing Exception Handling
 
-Invoking an API, which can throw an exception without the try-catch clause is notified as an WebAPIError and the analysis proceeded.
+Invoking an API which can throw an exception without the try-catch clause is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the tizen.calendar.getCalendars() is a function that can throw exceptions, so it must be wrapped by a try-catch statement. Because the try-catch statement does not exist, the JSA detects it and creates an alarm.
+In the following example, the tizen.calendar.getCalendars() function can throw exceptions, so it must be wrapped by a try-catch statement. Because the try-catch statement does not exist, the JSA detects it and raises an alarm.
 
  /*
@@ -577,9 +577,9 @@ tizen.calendar.getCalendars('EVENT', calendarListCallback, errorCallback);
 
 Rule 5. Wrong Argument Type
 
-Invoking API which passes wrong type value is notified as an WebAPIError and the is proceeded.
+Invoking an API which passes the wrong value type is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the tizen.contact.getAddressBooks() function needs arguments whose type is the function instead of the string and the undefined, so the JSA detects it and makes an alarm.
+In the following example, the tizen.contact.getAddressBooks() function needs arguments whose type is function instead of string and undefined, so the JSA detects it and raises an alarm.
 
  var addressBooksCB = 'notFucntion';
@@ -603,9 +603,9 @@ try {
 
 Rule 6. Wrong Dictionary Type
 
-Creating a dictionary object with wrong key-value pairs is notified as an WebAPIError and the is proceeded.
+Creating a dictionary object with the wrong key-value pairs is detected as an WebAPIError, although the analysis proceeds without stopping.
 
-In the following example, the constructor tizen.Contact() function needs a dictionary object as the first argument. If the keys of the dictionary object are different from the spec, the JSA detects it and creates an alarm.
+In the following example, the constructor tizen.Contact() function needs a dictionary object as the first argument. If the keys of the dictionary object are different from the spec, the JSA detects it and raises an alarm.
 
  var validContactObj = new tizen.Contact({
@@ -636,7 +636,7 @@ var invalidContactObj = new tizen.Contact({
 
 Invoking an API which is not defined in the current API version is noticed, although the analysis proceeds without stopping. If the Web API was defined in another API version or platform, the version name is provided in the error message.
 
-In the following example, the Web App is developed for the Tizen 2.3 wearable platform, but the tizen.archive.open() function is defined in for the Tizen 2.3 mobile platform, so the JSA detects it and creates an alarm.
+In the following example, the Web App is developed for the Tizen 2.3 wearable platform, but the tizen.archive.open() function is defined in the Tizen 2.3 mobile platform, so the JSA detects it and raises an alarm.
 
  function onsuccess() { /* ... */ }
@@ -664,7 +664,7 @@ try {
 
 To use a privileged Tizen Device API on a target device, the config.xml file of the Tizen Web application must have a corresponding privilege URL defined. An alarm is raised if the privilege is not found in the config.xml file.
 
-In the following example, the Web application is using the tizen.application.launch() function, which requires the http://tizen.org/privilege/application.launch privilege, which is commented in the config.xml file. So an alarm is raised.
+In the following example, the Web application is using the tizen.application.launch() function, which requires the http://tizen.org/privilege/application.launch privilege. It has been commented out in the config.xml file, so an alarm is raised.
 
 
 @@ -691,13 +691,13 @@ tizen.application.launch('targetApp0.main', onsuccess);
 
 
 Select the testing platform:
-In the Tizen device mode, the project is packaged as an application first, and then pushed to the Tizen device. Finally, it is launched automatically. After the application is launched, you can test the application.
+In the Tizen Device mode, the project is packaged as an application first, and then pushed to the Tizen device. The application launches automatically, allowing you to test it.
 In the PC Browser mode, the Web application runs at http://localhost:8888.
 
-When all operations are finished on the Tizen device or PC browser, click Stop Recoding on the Console view toolbar or enter Alt+Shift+T on the keyboard.
+
When all operations are finished on the Tizen device or PC browser, click Stop Record on the Console view toolbar or press Alt + Shift + T on the keyboard.
 
 
-After you stop recording, a confirmation message os displayed. Click OK.
+
After you stop recording, a confirmation message is displayed. Click OK.
 The Stale Object Checker continues to inspect the data collected and launches a result page at http://localhost:9000. The result page can be accessed by any Web browser in the PC.
 
 
@@ -715,11 +715,11 @@ tizen.application.launch('targetApp0.main', onsuccess);
         Kind: Site allocates a DOM object, a FUNCTION, or a regular OBJECT.
         Leak: Leak means that the count of stale instances is increasing over the execution lifetime.
     
-A stale instance is any instance whose staleness value is not zero sat a specific time. The object staleness defines the time interval between the last use and the moment when the object is unreachable. For example, if the object has never been used, the staleness is the unreachable moment minus the creation time. If the object has been used, the staleness is the unreachable moment minus the last use time.
+A stale instance is any instance whose staleness value is not zero at a specific time. The object staleness defines the time interval between the last use and the moment when the object is unreachable. For example, if the object has never been used, the staleness is the unreachable moment minus the creation time. If the object has been used, the staleness is the unreachable moment minus the last use time.
 
 Issue Table
 
-When you click a site in the issue table, a set of detailed information on a leak occurrence is shown. In the source view, you can easily find the code segment that steadily creates stale objects (possibly causing a memory leak), since it is marked with a colored box.
+When you click a site in the issue table, a set of detailed information on a leak occurrence is shown. In the source view, the code segment that is creating stale objects (possibly causing a memory leak) is marked with a colored box.
 
 Figure: Detailed information
 
@@ -730,8 +730,8 @@ tizen.application.launch('targetApp0.main', onsuccess);
 
In the call tree view, a call hierarchy is shown for the function which contains the code that creates stale objects. The name of a node in the call tree view indicates the file name, line number, and column number.
 The "js/main_orig_.js:10:45" root element indicates that the memory leak occurs at line 10, column 45 in the js/main_orig_.js file.
 Click the root element to move the source view to the location. Click the "js/main_orig_.js:27:5" child node to move the source view to line 27 where the function that contains the memory leak issue is called, and to highlight the function.
-In the timeline view, the x axis represents the time elapse and the y axis represents the number of created objects from this site. Move the mouse to a specific time to show the number of stale and allocated instances on the graph.
-In the access paths view, you can find out the scope of an object at runtime which leads to the location of the memory leak.

In the timeline view, the X axis represents the elapsed time and the Y axis represents the number of created objects from this site. Move the mouse to a specific time to show the number of stale and allocated instances on the graph.
In the access paths view, you can find out the scope of an object at runtime, which can lead to the location of the memory leak.

All-Sites Timeline

When you click start, the Timer starts to run. If you click again, the timer stops. The exitApp() function registers an event handler for the Tizen Back key to terminate the application when the Back key is pressed.

In the runtime() function, the exitApp() function is added by mistake. As a result, every time you click start, the exitApp() function is called, creates an anonymous function, and registers it to listen to the Back key events. When you test this application with the Stale Object Checker, multiple start button clicks are shown as a memory leak.

In the runtime() function, the exitApp() function is added by mistake. As a result, every time you click start, the exitApp() function is called, creates an anonymous function, and registers it to listen for the Back key events. When you test this application with the Stale Object Checker, multiple start button clicks are shown as a memory leak.

 /* JavaScript snippets */
@@ -766,7 +766,7 @@ function runtime() {
 }

When testing the source code, the following figure shows the result. It indicates that a memory leak occurred at the "js/main_orig_.js:39:42" site. Clicking this site, the detailed information is retrieved.

After testing the source code, the following figure shows the result. It indicates that a memory leak occurred at the "js/main_orig_.js:39:42" site. Click the site to retrieve details about the leak.

Figure: Timer example issue table

Figure: Timer example detailed information

Timer example detailed information

The detailed information shows that function object added to listen for "tizenhwkey" events caused a memory leak. If you click the "Call Tree" on the page, you can see that the exitApp() function with a memory leak issue is called in the runtime() function.

The detailed information shows that the function object added to listen for "tizenhwkey" events caused a memory leak. If you expand the "Call Tree" on the page, you can see that the exitApp() function with the memory leak issue is called in the runtime() function.

This code site is detected as a leak because the handler function objects created from the site have not been used before the application exits. The call tree says that when the runtime() function is executed, the exitApp() function is invoked, every time creates an anonymous function and registers it to a document object.

This code site is detected as a leak because the handler function objects created from the site have not been used before the application exits. The call tree says that when the runtime() function is executed, the exitApp() function is invoked, creating an anonymous function and registering it to a document object.

In the "Timeline" graph, you can see how the number of stale instances increases steadily. This graph shows any objects created from this code site that have not been used before the application exists.

In the "Timeline" graph, you can see how the number of stale instances increases steadily. This graph shows any objects created at this code site that have not been used before the application exits.

Calculator Sample Code

When you click a number button, the command() function is executed. The init() function registers an event handler for the Tizen Back key.

In the command() function, the init() function is added by mistake. As a result, every time you click a number button, the init() function is called, creates an anonymous function, and registers it to listen to Tizen Back key events.

When you test this application with the Stale Object Checker and click a number button many times, the problem is diagnosed as a memory leak. When testing the source code, the result is the same as in the Timer example above.

diff --git a/org.tizen.studio/html/web_tools/previewer_w.htm b/org.tizen.studio/html/web_tools/previewer_w.htm
index aa4bd4b..29c514b 100644
--- a/org.tizen.studio/html/web_tools/previewer_w.htm
+++ b/org.tizen.studio/html/web_tools/previewer_w.htm
@@ -47,8 +47,8 @@
 
 About the Previewer
 
-The Tizen Studio provides the previewer window for instantly previewing the entire look and feel of the application.
-The previewer for HTML and CSS is a tool that can check the content of a file on the browser. All the changes made in the HTML and CSS file editor are automatically reflected in the previewer.
+The Tizen Studio provides a previewer window for instantly previewing the entire look and feel of the application.
+The previewer for HTML and CSS is a tool that can check the content of a file in the browser. All changes made in the HTML and CSS file editor are automatically reflected in the previewer.
 
 The following limitations apply to the HTML previewer:
 	
diff --git a/org.tizen.studio/html/web_tools/privilege_checker_w.htm b/org.tizen.studio/html/web_tools/privilege_checker_w.htm
index d403762..fb7abe1 100644
--- a/org.tizen.studio/html/web_tools/privilege_checker_w.htm
+++ b/org.tizen.studio/html/web_tools/privilege_checker_w.htm
@@ -95,7 +95,7 @@
 
 
     Note
-	The Privilege Checker tool is based on the Content Assist Engine of the Tizen Studio. It is used for codes that are not supported by Content Assist and cannot be checked. Therefore, the check results can possibly have missing (unsound) values.
+	The Privilege Checker tool is based on the Content Assist engine in the Tizen Studio. It is used for code that is not supported by Content Assist and cannot be checked. Therefore, the check results can possibly have missing (unsound) values.
 
 
 
diff --git a/org.tizen.studio/html/web_tools/project_wizard_w.htm b/org.tizen.studio/html/web_tools/project_wizard_w.htm
index af43027..391ed1b 100644
--- a/org.tizen.studio/html/web_tools/project_wizard_w.htm
+++ b/org.tizen.studio/html/web_tools/project_wizard_w.htm
@@ -42,7 +42,7 @@
 
 The Tizen Project Wizard is a Tizen Studio tool that is used to create a Web application project.
 The Tizen Studio provides various project templates and samples that make it easier for you to start coding your application. When you create a new project, you can select a specific template, which the Tizen Project Wizard uses to automatically create basic functionalities for the application. The default project files and folders are also created.
-In the Tizen Project Wizard, you can select a profile and version, application type, and templates and sample type to create the project. In addition, you can set basic project properties, such as the project name, location, and working sets.
+In the Tizen Project Wizard, you can select a profile and version, application type, and template or sample to create the project. In addition, you can set basic project properties, such as the project name, location, and working sets.
 To open the Tizen Project Wizard, use one of the following:
 
 In the Tizen Studio menu, select File > New > Tizen Project.
@@ -57,23 +57,28 @@
 Figure: Selecting the project type
 
 
-The Tizen Studio provides various project templates and samples for the mobile and wearable devices according to the installed platform. The Tizen Project Wizard helps you select the template and sample for your project.
+The Tizen Studio provides various project templates and samples for mobile and wearable devices according to the installed platform. The Tizen Project Wizard helps you select a template or sample for your project.
 The Template option provides a list of templates with a basic structure where you can start the Web application project:
 
+Common
+	
+      Basic UI: Empty template project for developing basic UI applications.
+   
+
 Mobile
-	Basic UI: empty template project for developing basic applications.
-	TAU MasterDetail: empty template project for developing UI applications using TAU (Tizen Web UI Framework).
-	TAU MultiPage/SinglePage/Navigation: empty template project for developing multiple and single page applications and navigation applications using TAU.
+	
+	TAU MasterDetail: Empty template project for developing UI applications using TAU (Tizen Web UI Framework).
+	TAU MultiPage/SinglePage: Empty template projects for developing multiple page and single page applications using TAU.
 	
 
 Wearable
-	Basic UI: empty template project for developing basic UI applications.
-	TAU Basic: empty template project for developing basic circular UI applications using TAU.
-	TAU List: empty template project for developing UI applications using a TAU list.
+	
+	TAU Basic: Empty template project for developing basic circular UI applications using TAU.
+	TAU List: Empty template project for developing UI applications using a TAU list.
 	
-	Web Input Method Editor: empty template project for developing Web-based IME (Input Method Editor) applications using HTML, CSS, and JavaScript code.
+	
Web Input Method Editor: Empty template project for developing Web-based IME (Input Method Editor) applications using HTML, CSS, and JavaScript code.
 	
-	Widget: empty template project for developing widget applications.
+	
Widget: Empty template project for developing widget applications.
 	
 
 
@@ -137,7 +142,7 @@
  
  
  Working sets
- If you want to include the project to a specific working set, select a working set.
+ If you want to include the project to a specific working set, select a working set.
  
  
 
diff --git a/org.tizen.studio/html/web_tools/rest_viewer_w.htm b/org.tizen.studio/html/web_tools/rest_viewer_w.htm
index b0e29bd..7fd59df 100644
--- a/org.tizen.studio/html/web_tools/rest_viewer_w.htm
+++ b/org.tizen.studio/html/web_tools/rest_viewer_w.htm
@@ -28,7 +28,6 @@
 		
 		Content
 		
-			About the REST Viewer
 			Using the REST Viewer
 			Creating and Managing WADL Components
 			Authenticating the Application
@@ -41,27 +40,26 @@
 
  Using the REST Viewer
 
-With the Tizen Studio, you can use RESTful Web services. The REST Viewer provides facilities to emulate interaction with a Web service by composing and running requests, as if it was the application that actually calls the service.
+With the Tizen Studio, you can use RESTful Web services. The REST Viewer allows you to emulate interaction with a Web service by composing and running requests as if it were an application actually calling the service.
 
-About the REST Viewer
 The REST Viewer supports the testing, test case management, and the automatic code generation features of the REST API. You can easily develop Web applications using the REST API.
 
-The benefits of the REST Viewer:
+The REST Viewer offers the following benefits:
 
-It solves the inconvenience of the existing development process.
-It is a basic test and test history management tool without the need for additional test tools.
-The automatic code generation features improve code productivity.
-You do not need to implement a REST API call unit code. Besides, it automatically updates whenever the specification of the REST API changes.
+It addresses an inconvenience of the existing development process.
+It provides a complete basic testing and test history management tool, without the need for additional testing tools.
+The automatic code generation features improve coding productivity.
+You do not need to implement a REST API call unit code. It automatically updates whenever the specification of the REST API changes.
 
 
 There are 2 main use cases when you need to compose and run requests to a RESTful Web service:
 
 When you have developed a RESTful Web service and want to make sure it works as expected: that it is accessible in compliance with the specification and that it responds correctly.
-When you are developing an application that addresses a RESTful Web service. In this case, it is helpful to investigate the access to the service and the required input data before you start the development. During the development, you can also call the Web service from outside your application. This can help locate errors when your application results in unexpected output while no logical errors are detected in your code and you suspect that the bottleneck is the interaction with the Web service.
+When you are developing an application that addresses a RESTful Web service. In this case, it is helpful to investigate the access to the service and the required input data before you start development. During development, you can also call the Web service from outside your application. This can help locate errors where your application gives unexpected output even though no logical errors are detected in your code, and you suspect that the bottleneck is the interaction with the Web service.
 
 
 Using the REST Viewer
-The REST Viewer displays the components of the WADL (Web Application Description Language)  document in a hierarchical structure.
+The REST Viewer displays the components of the WADL (Web Application Description Language) document in a hierarchical structure.
 The viewer loads the documents from a specific location and classifies them as 4-typed WADL components.
 
 Figure: REST Viewer
@@ -78,7 +76,7 @@
 To open the REST Viewer settings, go to Preferences > Tizen Studio > REST Viewer, or click the  icon on the REST Viewer view toolbar.
 
 Creating and Managing WADL Components
-To use the REST Viewer, you need WADL. If WADL provided by the REST API service providers exists, it can be used to import. When you export a test case, others can be used.
+To use the REST Viewer, you need a WADL document. If a WADL document is provided by the REST API service provider, you can import it. You can also export a test case so that others can use it.
 With the REST Viewer, you can make new WADL components, and import and export WADL files. You can handle a selected WADL component only if you open a dialog to modify it. You cannot modify the selected component's parent or child components at the same time.
 
 
@@ -131,7 +129,7 @@
 
 
 Authenticating the Application
-The REST Viewer helps when you test the application with authentication.
+The REST Viewer can help you test applications that require authentication services.
 To test the authentication, go to Preferences > Tizen Studio > REST Viewer > Authentication, and select Use authentication.
 In the same location, you can define the authentication details:
 
@@ -147,17 +145,17 @@
 You can test the selected API on the REST Viewer and view the results.
 You can run a test using 1 of the following options:
 
-Click the  icon on the REST Viewer view toolbar. The view displays the running history.
+Click the  icon on the REST Viewer view toolbar. The view displays the run history.
 Right-click the selected API and run the test from the context menu.
 Click Save and Run in the dialog when adding or modifying components.
 
-The API that works with variables needs specific values for the test. Each profile has its own user variables (key and value). You can manage the profiles and user variables in the Preferences window. After the user variables are set, you can use them with a placeholder to test the API (for example, ${email}).
+APIs that work with variables need specified values for testing. Each profile has its own user variables (key and value). You can manage the profiles and user variables in the Preferences window. After the user variables are set, you can use them with a placeholder to test the API (for example, ${email}).
 
 Figure: User variables
 
 
 
-You can select an active profile in the REST Viewer user variable toolbar menu. When you test the APIs in the REST Viewer, user variables of the selected profile are used.
+You can select an active profile in the REST Viewer user variable toolbar menu. When you test the APIs in the REST Viewer, the user variables of the selected profile are used.
 
 Figure: Selecting a profile
 
@@ -181,7 +179,7 @@
 Drag and drop:
 	
 	Select the API model in the REST Viewer, and drag and drop it to the Web HTML Editor.
-	Select the functions at bottom of the dialog to get the code.
+	Select the functions at the bottom of the dialog to get the code.
 	
 
 
diff --git a/org.tizen.studio/html/web_tools/web_editor_w.htm b/org.tizen.studio/html/web_tools/web_editor_w.htm
index 2df6e11..97bdd13 100644
--- a/org.tizen.studio/html/web_tools/web_editor_w.htm
+++ b/org.tizen.studio/html/web_tools/web_editor_w.htm
@@ -146,7 +146,7 @@
 
 
 Advanced Content Hover in Mobile Applications
-The advanced content hover supports additional information on the attribute values of some elements in the HTML editor.
+The advanced content hover displays additional information on the attribute values of some elements in the HTML editor.
 The advanced content hover has the following features:
 
 Supports a preview at the href attribute value of the <a> element.
@@ -170,11 +170,11 @@
 The advanced file refactoring has the following features:
 
 File rename refactoring
-When a file is renamed, other files to which the renamed file is related, are changed at the linked line of codes.
+When a file is renamed, other files to which the renamed file is related are changed at the linked code line.
 File move refactoring
-When a file is moved, other files to which the moved file is related, are changed at the linked line of codes.
+When a file is moved, other files to which the moved file is related are changed at the linked code line.
 File delete refactoring
-When a file is deleted, other files to which the deleted file is related, are commented out at the linked line of codes.
+When a file is deleted, other files to which the deleted file is related are commented out at the linked code line.
 
 Figure: Before CSS file rename refactoring
 
@@ -184,7 +184,7 @@
 
 Previewer
 To test a Web application, or a single Web page as part of a client application, use the previewer window.
-You can preview that you have developed the source code quickly. In addition, it is possible to visually define the type and hierarchy of the selector, which helps development.
+Not only can you preview the source code you have developed, you can also visually define the type and hierarchy of the selector to help development.
 For more information, see Previewing Pages in a Browser.
 
 Using JavaScript Log Console View
@@ -230,7 +230,7 @@
 Code Beautifier and Minifier
 The Code Beautifier is a tool that can help you understand code and make it easier to read.
 The Code Minifier is a smart compression tool. Minification is the process of compressing code from the original size to the smallest size without affecting its operation.
-For more information, see Improving Your Code Productivity.
+For more information, see Cleaning Up Your Code.
 
 Web Unit Testing
 If you are implementing a component in your application, you must test it to ensure that it does not behave in an unexpected way.
diff --git a/org.tizen.studio/html/web_tools/web_inspector_w.htm b/org.tizen.studio/html/web_tools/web_inspector_w.htm
index 9c355d9..7f89200 100644
--- a/org.tizen.studio/html/web_tools/web_inspector_w.htm
+++ b/org.tizen.studio/html/web_tools/web_inspector_w.htm
@@ -80,7 +80,7 @@
   
 
  Timeline Panel
-  The Timeline panel of the JavaScript Debugger allows you to perform advanced timing and speed analysis. You can see how long the browser takes to handle DOM events, and rendering and painting windows.
+  The Timeline panel of the JavaScript Debugger allows you to perform advanced timing and speed analysis. You can see how long the browser takes to handle DOM events, and render and paint windows.
   Figure: Timeline panel
   
 
diff --git a/org.tizen.studio/index.xml b/org.tizen.studio/index.xml
index 3f68180..1ea62fc 100644
--- a/org.tizen.studio/index.xml
+++ b/org.tizen.studio/index.xml
@@ -90,11 +90,11 @@
 			
 			
 		
-		
+		
 			
 			
 			
-			
+			
 			
 			
 			
-- 
2.7.4

Specfile Editor

Content Assist

Using API Link

Flashing the Project

Setting Tizen Studio Web Preferences

Setting Web Preferences

Editor

Configuration Editor

National Language Support

Launch

Improving Your Code Productivity

Cleaning Up Your Code

Using the Code Beautifier

Using the Code Minifier

Configuring Applications

Configuration Elements

Extending Configuration Elements in Mobile Applications

Extending Configuration Elements in Wearable Applications

Speeding Up Typing with Content Assist

Adding User-defined APIs

Writing and Editing Codes

Writing and Editing Code

Rule 1. Use var to declare variables

Rule 2. Do Not Declare an Arguments Array within Functions

Rule 3. Do Not Capture Variables in Functions

Rule 4. Do Not Use Extra Semicolons

Rule 5. Do Not Use the Delete Keyword

Rule 8. Do Not Modify the Prototypes of Built-in Objects

Rule 10. Do Not Use the for-in Structure with Arrays

Rule 11. Do Not Use Unclosed Braces

Rule 12. Do Not Use Unclosed Comments

Rule 13. Do Not Use Unclosed Strings

Rule 14. Do Not Omit Semicolons

Rule 15. Do Not Begin With Operators

Web API Usage Rules

Rule 1. Accessing Undefined API

Rule 2. Wrong Argument Number

Rule 3. Missing Error Handling

Rule 4. Missing Exception Handling

Rule 5. Wrong Argument Type

Rule 6. Wrong Dictionary Type

Issue Table

All-Sites Timeline

Calculator Sample Code

About the Previewer

Using the REST Viewer

About the REST Viewer

Using the REST Viewer

Creating and Managing WADL Components

Authenticating the Application

Advanced Content Hover in Mobile Applications

Previewer

Using JavaScript Log Console View

Code Beautifier and Minifier

Web Unit Testing

Timeline Panel

Rule 1. Use `var` to declare variables

Rule 10. Do Not Use the `for-in` Structure with Arrays