anchor.diff:  
  -Red Hat JBoss BPM Suite comes with a plug-in for Red Hat JBoss Developer Studio to provide support for the development of business processes in the Eclipse-based environment, such as debugging and testing. It also provides a graphical Process Designer for business process editing.
  +Red Hat JBoss BPM Suite comes with a plug-in for Red Hat JBoss Developer Studio that provides support for development of business processes in the Eclipse-based environment, such as debugging and testing. It also provides a graphical Process Designer for business process editing.
   
  -Note that the repository structure follows the maven structure and is described in xref:_assets_projects_gloss_chap-project[].
  +The repository structure follows the maven structure described in xref:_assets_projects_gloss_chap-project[].
   
   For instructions on how to install and set up the plug-in, see the _{INSTALLATION_GUIDE}_.
   
   = Creating BPM Project
   
   .Prerequisite
  -Ensure that you have installed Red Hat JBoss BPM Suite and Red Hat JBoss BRMS plug-ins and runtime environments. For more information, see _{INSTALLATION_GUIDE}_.
  +You must have Red Hat JBoss Developer Studio with both Red Hat JBoss BPM Suite and Red Hat JBoss BRMS plug-ins and runtime environments installed. For more information, see _{INSTALLATION_GUIDE}_.
   
   To create a BPM project:
   
  -. On the main menu of Red Hat JBoss Developer Studio, click *File* -> *New* -> *Other...*.
  -. Choose *jBPM* -> *jBPM project*.
  +. In the Red Hat JBoss Developer Studio menu, click *File* -> *New* -> *Other...*.
  +. Click *jBPM* -> *jBPM project*.
   . In the *Create New jBPM Project* dialog, select the required content and click *Next*.
  -. If you did not decide for project with online examples, specify the project name, location, and type:
  +. If you did not select a project with online examples, specify the project name, location, and type:
   * `Java and jBPM Runtime classes`: select the runtime to be used by the project or click *Manage Runtime Definitions...* and define a new runtime (for details on runtime resources, see the _{INSTALLATION_GUIDE}_).
   * `Maven`: specify maven properties of your project.
   
  
positive.code: 
  . Choose *File* -> *New* -> *Other...*.
  . Select *jBPM* -> *jBPM Process Diagram*.
  . In the displayed dialog box, define the name, package, and container of the process. The rest of the fields is completed automatically. Note that you must follow the Maven structure.
  
  Once created, the process is opened for editing in the graphical Process Designer.
  
  [[_checking_session_logs]]
  = Checking Session Logs
  
  You can check the session logs in the audit log, which is a log of all events that were logged from the session. Audit log is an XML-based log file which contains a log of all the events that occurred while executing a specific ksession.
  
  .Procedure: Creating Logger
  . To create a logger, use `KieServices` and attach the logger to a `ksession`, for example:
  
negative.code: // Do something with the ksession here.
  logger.close();
  ----
  . Always close the logger when you have finished using it.
  
  .Procedure: Using Audit View
  . To use *Audit View*, click *Window* -> *Show View* -> *Other...*.
  . Click the *Drools*, and click *Audit*.
  . To open a log file in *Audit View*, select the log file using the *Open Log* action in the top right corner, or simply drag and drop the log file from the _Package Explorer_ or _Navigator_ into the _Audit View_.
  . A tree-based view is generated based on the data inside the audit log. Depicted below is an example tree-based view:
  +
  .Tree-Based View
  image::5025.png[An example tree-based view for Audit log.]
  . An event is shown as a subnode of another event if the child event is caused as a direct consequence of the parent event.
  
  [NOTE]
  .File-Based Logger
  ====
  The file-based logger will only save the events on close (or when a certain threshold is reached). If you want events to be saved at regular intervals (such as during debugging), use a threaded file logger so the audit view is updated to show the latest state. When creating a threaded file logger, you can specify the interval after which events should be saved to the file (in milliseconds).
  ====
  