[ 
https://issues.apache.org/jira/browse/CB-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155242#comment-15155242
 ] 

ASF GitHub Bot commented on CB-9478:
------------------------------------

Github user sarangan12 commented on a diff in the pull request:

    https://github.com/apache/cordova-docs/pull/510#discussion_r53539411
  
    --- Diff: www/docs/en/dev/guide/next/index.md ---
    @@ -62,7 +62,7 @@ And many, many, more.
     
     One of the biggest mistakes a new Cordova developer can make is to assume 
that the performance they get on a desktop machine is the same they will get on 
a mobile device. While our mobile devices have gotten more powerful every year, 
they still lack the power and performance of a desktop. Mobile devices 
typically have much less RAM and a GPU that is a far cry from their desktop (or 
even laptop) brethren. A full list of tips here would be too much, but here are 
a few things to keep in mind (with a list of longer resources at the end for 
further research).
    --- End diff --
    
    Can we rephrase this somehow? Like: "Use the following tips to improve the 
performance in mobile..." instead of comparing it with desktops,


> Minor problems with Next Steps page
> -----------------------------------
>
>                 Key: CB-9478
>                 URL: https://issues.apache.org/jira/browse/CB-9478
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: Master
>            Reporter: Kevin Christopher Henry
>            Assignee: Raghav
>            Priority: Minor
>              Labels: Docs-6.x, triaged
>
> I noticed two documentation bugs on the Next Steps page:
> 1) The "Fastouch" library is mentioned. I assume that FastClick is meant?
> 2) Malformed HTML for the "Fast Apps and Sites with JavaScript" link.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to