diff --git a/docs/status.md b/docs/status.md
index e1a5d34..5c2f2e8 100644
--- a/docs/status.md
+++ b/docs/status.md
@@ -301,7 +301,7 @@
 The `_FORTIFY_SOURCE` macro can be used to enable extra
 automatic bounds checking for common libc functions. If a buffer
 overrun is detected, the program is safely aborted as in this
-(example)[https://source.android.com/devices/tech/debug/native-crash#fortify].
+[example](https://source.android.com/devices/tech/debug/native-crash#fortify).
 
 Note that in recent releases Android's FORTIFY has been extended to
 cover other issues. It can now detect, for example, passing `O_CREAT`
@@ -313,7 +313,7 @@
 all result in FORTIFY failures even for code not built with FORTIFY.
 
 More background information is available in our
-(FORTIFY in Android)[https://android-developers.googleblog.com/2017/04/fortify-in-android.html]
+[FORTIFY in Android](https://android-developers.googleblog.com/2017/04/fortify-in-android.html)
 blog post.
 
 The Android platform is built with `-D_FORTIFY_SOURCE=2`, but NDK users
diff --git a/linker/ldd b/linker/ldd
index 3a0aff9..6bc49b4 100644
--- a/linker/ldd
+++ b/linker/ldd
@@ -10,7 +10,8 @@
 
 [ $# -eq 1 ] || error "usage: ldd FILE"
 
-case `file -L "$1"` in
+what=$(file -L "$1")
+case "$what" in
   *32-bit*)
     linker --list "$1"
     ;;
@@ -18,6 +19,6 @@
     linker64 --list "$1"
     ;;
   *)
-    error "$1: not an ELF file"
+    error "$what"
     ;;
 esac