anchor.diff:    :marked
       **Do** create services with a single responsibility that is encapsulated by its context.
       
  -    **采用** 新建单一职责的服务，封装在它的环境内。
  +    **坚持** 新建单一职责的服务，把它封装在自己的环境内。
   
   .s-rule.do
     :marked
       **Do** create a new service once the service begins to exceed that singular purpose.
       
  -    **采用** 当一个服务成长到超出一个用意时，新建一个服务。
  +    **坚持** 当服务成长到超出一个用意时，新建一个服务。
   
   .s-why
     :marked
       **Why?** When a service has multiple responsibilities, it becomes difficult to test.
       
  -    **为何？** 当一个服务有多个职责时，它很难被测试。
  +    **为何？** 当服务有多个职责时，它很难被测试。
   
   .s-why.s-why-last
     :marked
       **Why?** When a service has multiple responsibilities, every Component or Service that injects it now carries the weight of them all.
       
  -    **为何？** 当一个服务有多个职责时，每个注入它的组件或者服务都承担了它们（多个职责）所有的重量。
  +    **为何？** 当服务有多个职责时，每个注入它的组件或者服务都会被迫承担它们的（多个职责）所有的重量。
   
   a(href="#toc") Back to top
   
  
positive.code: 
    Client-side routing is important for creating a navigation flow between a component tree hierarchy, and composing components that are made of many other child components.
    
    在组件树阶层间创建一个导航流和在组合多个子级组件组成的组件时，客户端路由是很重要的。
  
  a(href="#toc") Back to top
  
  
negative.code: .l-main-section
  :marked
    ### End to End Test File Names
    ### 端对端测试文件命名
    <a id="02-11"></a>
    #### Style 02-11
    #### 风格02-11
  