| Index: native_client_sdk/src/doc/devguide/coding/3D-graphics.rst
|
| diff --git a/native_client_sdk/src/doc/devguide/coding/3D-graphics.rst b/native_client_sdk/src/doc/devguide/coding/3D-graphics.rst
|
| index 6bd800ba4d4521dbf7c7164acadb01556d15c4d2..7563a0f77fa63bf4711ef71465d1a032aab15bfb 100644
|
| --- a/native_client_sdk/src/doc/devguide/coding/3D-graphics.rst
|
| +++ b/native_client_sdk/src/doc/devguide/coding/3D-graphics.rst
|
| @@ -160,7 +160,7 @@ code should describe the issue as clearly as possible. That's easy if there is a
|
| missing feature. Failure to create a graphics context is tougher to diagnose. At
|
| the very least, you can suggest that the user try to update the driver. You
|
| might want to linke to the Chrome page that describes `how to do updates
|
| -<http://support.google.com/chrome/bin/answer.py?hl=en&answer=1202946>`_.
|
| +<https://support.google.com/chrome/answer/1202946>`_.
|
|
|
| If a user can't update the driver, or their problem persists, be sure to gather
|
| information about their graphics environment. Ask for the contents of the Chrome
|
|
|