Fix linter.

Author: onurtemizkan

packages/e2e-tests/test-applications/create-remix-app-v2/.eslintrc.js

@@ -1,4 +1,4 @@
 /** @type {import('eslint').Linter.Config} */
 module.exports = {
-  extends: ["@remix-run/eslint-config", "@remix-run/eslint-config/node"],
+  extends: ['@remix-run/eslint-config', '@remix-run/eslint-config/node'],
 };

packages/e2e-tests/test-applications/create-remix-app-v2/README.md

@@ -39,9 +39,12 @@ Make sure to deploy the output of `remix build`
 
 ### Using a Template
 
-When you ran `npx create-remix@latest` there were a few choices for hosting. You can run that again to create a new project, then copy over relevant code/assets from your current app to the new project that's pre-configured for your target server.
+When you ran `npx create-remix@latest` there were a few choices for hosting. You can run that again to create a new
+project, then copy over relevant code/assets from your current app to the new project that's pre-configured for your
+target server.
 
-Most importantly, this means everything in the `app/` directory, but if you've further customized your current application outside of there it may also include:
+Most importantly, this means everything in the `app/` directory, but if you've further customized your current
+application outside of there it may also include:
 
 - Any assets you've added/updated in `public/`
 - Any updated versions of root files such as `.eslintrc.js`, etc.